Recipes · Builders

Resend

Deliverability signals ready when you ask

Webhook important Resend events into email so Instinct hears bounces, failures, and complaints.

Recommended: Webhook to email your bot ~10 min setup

Outcome

Instinct can answer "Any bounces today?", "Did sends start failing?", or "Summarize deliverability events this week?" without living in the Resend dashboard.

What gets sent

  • Event type (email.bounced, email.failed, email.complained; optional email.delivered if you truly want volume)
  • Subject, from, to, email id when present
  • Failure or bounce reason when Resend includes it
  • Not required: every email.sent / email.opened (usually too noisy)

How to send

Goal: one email lands in your bot today.

Copy your Instinct bot address from Instinct → Settings.

Paste the address from Instinct → Settings.

On Instinct: Copy your bot address from Settings

In Resend: Webhooks → Add endpoint (Zapier Catch Hook or Make).

On Resend: Open Webhooks and add a Zapier or Make endpoint

Subscribe to high-signal types first: email.bounced, email.failed, email.complained. Add email.delivery_delayed only if useful.

On Resend: Subscribe to bounced, failed, and complained events

In Zapier/Make: Send email to the Instinct bot.

In Zapier or Make: Send webhook events by email to your bot

Subject/body: type, subject, recipient, reason, and timestamp (example subject Resend: {type} - {subject}).

In Zapier or Make: Add type, subject, recipient, reason, and timestamp

Send a webhook test and confirm Instinct got the event mail.

On Resend: Send a webhook test and confirm the event mail arrived
Subject: Resend: {type} - {subject} Type: {type} To: {to} From: {from} Reason: {reason} Email id: {email_id} When: {timestamp}
Other ways · Forward account/billing mail (thin for ops)

Forward any Resend account/billing emails you already receive. Thin for deliverability ops.

Other ways · Custom worker daily digest (more engineering)

Custom worker that aggregates webhooks into a daily digest email. Better long-term, more engineering.

Tips & gotchas

  • Weak path (honest): No native email digest to an arbitrary address. Webhook→email is required.
  • Start with failures only. email.delivered / email.opened will flood Instinct.
  • Verify webhook signatures in production; Zapier templates often handle this for you.
  • Instinct is a side channel. Keep dashboards or Slack for real-time on-call if volume is high.
  • Do not paste API keys into email bodies.

Try asking Instinct…

After a mail or two lands, try:

Any Resend bounces or failures today?

Summarize deliverability events from this week.

What was the last complaint or fail reason you saw?

Are failures spiking compared to yesterday?