Recipes · Builders

Netlify

Deploys without tab-hopping

Production deploy succeeded/failed mail so Instinct knows what's live without three dashboards.

Recommended: Netlify · native deploy email ~2 min setup

Outcome

You can ask Instinct "Did production deploy?" or "What failed last night?" and get an answer from the same thread where you plan fixes. Release context stays next to product and support notes instead of buried in three dashboards.

What gets sent

  • Project/site name, environment (production/preview), deploy status
  • Commit message / branch when the platform includes it
  • Error summary on failures; URLs to the deploy or logs
  • Timestamps

How to send

Goal: one email lands in your bot today.

Copy your bot address from Instinct → Settings.

On Instinct: Copy your bot address from Settings

Netlify site → Project configuration → Notifications → Deploy notifications.

On Netlify: Open Deploy notifications

Add notification for Deploy succeeded and Deploy failed (add others if useful).

On Netlify: Enable succeeded and failed emails

Choose Email, set recipient to your bot address.

On Netlify: Set recipient to your bot address

Trigger a deploy and confirm Instinct got both success and failure shapes.

On Netlify: Trigger a deploy and confirm in Instinct

Note: email deploy notifications are on Pro/Enterprise plans: on free tiers, use a webhook → Zapier Email instead.

Subject: "Deploy {status}: {project} ({environment})" Status: {status} Project: {project} Environment: {environment} Commit: {commit_message} URL: {deployment_url}
Other ways · Vercel (~10 min)

Native: Team/user Notifications: enable Deployment failures email (sent to the deployment owner). Forward those to your bot address with an inbox rule.

Success + custom: Vercel Settings → Webhooks → events like deployment.succeeded, deployment.error, deployment.canceled.

Point the webhook at Zapier Catch Hook (or Make) → action Send outbound email to your bot address.

Map project name, URL, target, and git commit message into the email body.

Other ways · Railway (~10 min)

Railway project → Settings → Webhooks → add a webhook URL (Zapier/Make Catch Hook).

On deployment status changes, Zapier Email → your bot address.

Include service name, status (SUCCESS/FAILED/CRASHED), and deployment ID/URL.

Railway's own emails skew toward failures/crashes: webhooks are the reliable path for success events too.

Tips & gotchas

  • Preview deploys can flood Instinct: filter to production only.
  • Don't paste auth tokens or .env contents into webhook test payloads.
  • If Netlify email isn't on your plan, don't fight it: webhook→email is the practical workaround.

Paste the address from Instinct → Settings. Don't email the placeholder.