Resend Inbound
Mail arrived at the assistant’s own domain (F23 v2 — Resend receiving).
Replaces the Gmail-filter → Pipedream bridge: notetaker.anyreach.ai has a
real MX now, Resend receives for it, and this route is where the
email.received webhook lands. Two trust improvements over the bridge —
the sender is an address Resend actually received mail from (SPF/DKIM
validated upstream, not asserted by whoever holds an HMAC secret), and
the Svix signature proves the event came from Resend. Same refuse-when-
unconfigured contract as every webhook beside it.
The event is metadata-only, so the full message is hydrated back from Resend’s API before extraction. A transient hydration failure answers 503 ON PURPOSE: Svix redelivers on non-2xx, and that retry is the only thing standing between a blip and a silently lost booking request. Everything downstream — vetting, dedup on message id, the attach-to- existing lookup, the lane choice, the running-workflow supersede — is the same path the old endpoint feeds; the two converge at the RPC.
Response
Successful Response
The response is of type Response Resend Inbound Meetings Webhooks Resend Inbound Post · object.