Integration · Resend

Verified Resend webhooks for your AI agent.

Resend webhook signature verification runs before persistence. Email lifecycle events (sent, delivered, bounced, complained, opened, clicked) get routed with full provider metadata.

Start freeProvider verification guide

Verification + metadata

What your agent receives

// Hooksbase verifies Svix-style signature for Resend webhooks
// Your agent receives:
{
  "provider": {
    "name": "resend",
    "sourceId": "email_...",
    "eventType": "email.bounced",
    "verified": true
  },
  "payload": { /* raw Resend event */ }
}

Routable metadata fields

Match on provider fields

Once Resendverification is enabled, these fields are available to routing rules, delivery search, and your agent's payload.

  • provider.name = "resend"
  • provider.sourceId = Resend email ID
  • provider.eventType = e.g. "email.delivered", "email.bounced"
  • provider.verified = boolean

Agent recipes

Common Resend + agent patterns

Deliverability-response agent

Route `email.bounced` events to an agent that tags the recipient as invalid and removes them from future sends.

Engagement-classification agent

Route `email.opened` / `email.clicked` events to an agent that scores recipients for follow-up.

Complaint-response agent

Route `email.complained` to a security-and-compliance agent that suppresses future sends and flags the template.

Get started

Point Resend at Hooksbase.

Configure the Resend provider pack on a Hooksbase webhook, copy the ingest URL, paste it into your Resend webhook settings. Every verified event lands with full provider metadata on the delivery.

Start freeRead the verification guide