Skip to main content
Resend covers outbound-only sending. Gork adds agent-native inboxes, inbound mail, threading, and MCP tools on top of a /v1 REST API. Migration is a clean swap in three passes.

1. Map the API calls

The SDK swap is one import:

2. Remap webhooks

Gork signs every delivery (X-Gork-Signature, HMAC-SHA256) — verify with verifyGorkWebhook instead of Resend’s Svix verifier. See Verify webhook requests. Retry policy: 5 attempts over 30s → 1h, 4xx terminal. See Retries.

3. Move suppressions and domains

  1. Export bounces/complaints/unsubscribes from Resend and replay them into POST /v1/suppressions ({email, reason}) so day-one sends respect prior opt-outs. See Suppressions.
  2. Add the domain in Gork, install the DNS records alongside Resend’s (both can coexist), verify, then cut traffic over gradually — keep both sending paths live during the transition and compare delivery in Email activity.
  3. Update SPF to include both providers during migration (include:amazonses.com), then remove the old one.
Gork has no bulk-campaign objects (Resend Audiences/Broadcasts map to per-recipient messages/send calls). If you send newsletters, budget the per-request loop and watch Rate limits: 240 req/min per workspace.