DextelDocs

Connect Resend

Simple API with receiving built in. Delivery events and inbound mail share one Svix-signed webhook.

Where this lives in Dextel

Agency: Agency → Integrations → Email Service (outbound only). Sub-account: Settings → Integrations → Email Integration (outbound + inbound). The modal shows the exact webhook URLs to paste into Resend; this page explains what to do with them.

Prerequisites

  • A Resend account and a domain you control (you'll add DNS records).
  • Owner or admin access to the Dextel agency or sub-account.
  • Credentials you'll enter in Dextel: API key (re_…).

1. Create the API credentials

  1. In Resend open API Keys → Create API Key.
  2. Choose Full access (a sending-only key can't read received mail).
  3. Copy the key (shown once) into Dextel → Settings → Integrations → Email.

Resend docs: API keys

2. Verify your sending domain

  1. Open Domains → Add Domain and enter your sending domain.
  2. Add the DKIM TXT (resend._domainkey), the SPF TXT and the send. MX record to your DNS.
  3. Click Verify and wait for the domain to show verified.
  4. Turn on open and click tracking under Domains → (your domain) → Tracking.

Then in Dextel enter a From email on that domain (for example hello@yourdomain.com) and a From name, and click Validate & Connect. Dextel checks the credentials against Resend before saving.

Resend docs: domains

3. Delivery events

Delivered, opened, clicked, bounced and spam events feed the Email Event workflow trigger and automatically unsubscribe contacts after a hard bounce or complaint. Copy the Webhook URL from the Delivery events tab in Dextel, then:

  1. Open Webhooks → Add Webhook.
  2. Paste <your delivery-events webhook URL> as the endpoint URL.
  3. Tick email.delivered, email.delivery_delayed, email.bounced, email.complained, email.opened and email.clicked — plus email.received if you use inbound.
  4. Open the webhook, copy its Signing Secret and paste it into the Delivery events tab in Dextel.
This provider signs its webhooks. Paste the signing secret / verification key into the Delivery events tab — Dextel rejects unsigned posts.

Use Send a test email in the same tab to confirm outbound works; the events pill turns green once the first event arrives.

Resend docs: webhooks

4. Inbound email (sub-accounts only)

Inbound turns contact replies into Inbox conversations and fires the Contact Replied — Email trigger. Mail is received at your saved From address, so when a contact hits Reply the message comes back through Resend to Dextel. The MX record routes all mail for that domain to Resend: if you already receive mail on the domain, send from an address on a subdomain (for example hello@mail.yourdomain.com).

Inbound mail arrives on the same webhook as delivery events — tick email.received on it.

DNS records

TypeHostValuePriority
MXyourdomain.com(value shown in the Resend Receiving modal)10

Steps

  1. In Domains, open your sending domain (yourdomain.com) and toggle Receiving on.
  2. Add the MX record Resend shows (priority 10) and click "I've added the record".
  3. Make sure email.received is ticked on the webhook from the previous section.
  4. Send a test email to your From address and watch for it in the Inbox.

Resend docs: inbound

Troubleshooting

  • "Domain not verified" on send — the from address must be on a verified domain; onboarding@resend.dev only works for testing.
  • Events show "Not set up" — paste the webhook's signing secret; without it Dextel rejects the posts with 503.
  • Still stuck? Compare with another provider on the Email Providers overview.