Integration · Resend
Verified Resend webhooks for your AI agent.
Hooksbase verifies each Resend webhook signature before persisting the delivery, stamps queryable provider metadata (event type, source ID, verified flag) on the event, and routes it to your AI agent — no webhook plumbing to build.
Resend webhook signature verification runs before persistence. Email lifecycle events (sent, delivered, bounced, complained, opened, clicked) get routed with full provider metadata.
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
Route `email.bounced` events to an agent that tags the recipient as invalid and removes them from future sends.
Route `email.opened` / `email.clicked` events to an agent that scores recipients for follow-up.
Route `email.complained` to a security-and-compliance agent that suppresses future sends and flags the template.
Frequently asked questions
- How do I verify Resend webhooks with Hooksbase?
- Resend signs webhooks with a Svix-style signature. Add the Resend provider pack to a Hooksbase webhook and paste your Resend signing secret; Hooksbase verifies the signature before the delivery is persisted, so only authentic Resend events reach your agent.
- Does Hooksbase check the Resend signature before my agent sees the event?
- Yes. Hooksbase validates the Svix-style Resend signature before persisting the delivery and sets `provider.verified = true`. Your agent only receives Resend events whose signature already matched your secret.
- Which Resend event types can I route on with Hooksbase?
- Hooksbase extracts the Resend event type into `provider.eventType` (for example `email.delivered`, `email.bounced`, `email.opened`, or `email.complained`), so you can route any email lifecycle event directly. The Resend email ID is captured as `provider.sourceId`.
- Can I send Resend events to multiple destinations from Hooksbase?
- Yes. Hooksbase can fan a single verified Resend event out to several typed destinations at once — for example a deliverability agent over HTTP plus GCP Pub/Sub or an S3-compatible archive — each with the full provider metadata attached.
- Can I replay a Resend webhook delivery in Hooksbase?
- Yes. Hooksbase retains delivery detail for 30 days and supports deterministic replay from the persisted dispatch snapshot, so you can re-run a verified Resend `email.bounced` event through your agent after a fix without waiting for another bounce.
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.