All docs

Setup guide

Connect Resend to Developer Inbox

Walk through API keys, domains, webhooks, and mailbox settings so inbound Resend mail shows up in Developer Inbox.

This guide walks you through receiving inbound email and sending replies with Resend and Developer Inbox.

Developer Inbox is not an email provider. Resend receives and sends mail; this app stores conversations and gives you a UI to read and reply.


What you will set up

  1. A Resend account and API key
  2. A domain (or Resend receiving address) for inbound mail
  3. A webhook from Resend → Developer Inbox
  4. A provider connection under Settings → Connection, plus optional extra addresses under Settings → Mailboxes

When finished, mail sent to your domain appears in the Inbox, and you can reply or compose from the app.


Prerequisites

  • Developer Inbox running locally or deployed (see the root README)
  • A Resend account
  • For production inbound: a domain you control (DNS access)
  • For local webhooks: a public HTTPS tunnel (e.g. ngrok, Cloudflare Tunnel, or Vercel preview URL)

Webhook URLs in Settings are built from the current request host. Open the app at the same public URL Resend will call (your Vercel domain, or the ngrok URL), and the webhook link is correct automatically.

Only set NEXT_PUBLIC_APP_URL if you browse via one host (e.g. localhost) but need Settings to show a different public URL (e.g. an ngrok tunnel):

# Optional override — usually not needed
NEXT_PUBLIC_APP_URL="https://your-subdomain.ngrok-free.app"

Step 1 — Create a Resend API key

  1. Open the Resend dashboard.
  2. Click Create API Key.
  3. Give it a name (e.g. developer-inbox).
  4. Choose full access (or at least send + receiving permissions).
  5. Copy the key (re_...) and store it securely — you will paste it into Developer Inbox Settings.

Step 2 — Set up a sending / receiving domain

  1. Go to Resend Domains.
  2. Add your domain (e.g. example.com or a subdomain like mail.example.com).
  3. Add the DNS records Resend shows (SPF, DKIM, and any others).
  4. Wait until the domain status is Verified.

Enable receiving (inbound)

  1. Open the domain details in Resend.
  2. Enable Receiving for that domain.
  3. Add the MX record Resend provides.

Important: MX must not conflict with an existing mailbox provider on the same hostname. If example.com already receives mail via Google/Microsoft, use a subdomain for Resend inbound (e.g. inbox.example.com) so you do not take over the root MX.

Once MX is correct, Resend accepts mail for any address at that domain (e.g. you@inbox.example.com, support@inbox.example.com).

Option B — Resend-managed receiving address

For quick tests, Resend can provide a *.resend.app receiving address. Use that if you only need to verify the webhook before setting up DNS.


Step 3 — Deploy or tunnel your webhook URL

Resend must POST to a publicly reachable HTTPS endpoint:

https://<your-app-host>/api/webhooks/resend/<connectionId>

<connectionId> is created in the next step inside Developer Inbox.

Local development

  1. Start the app: npm run dev
  2. Start a tunnel to port 3000
  3. Open Developer Inbox through the tunnel URL (so Settings copies a public webhook URL), or set optional NEXT_PUBLIC_APP_URL to the tunnel HTTPS URL

Production

Deploy to Vercel (or similar). Open Settings on your production host — the webhook URL uses that host automatically.


Step 4 — Connect Resend in Developer Inbox (3 steps)

Open Settings → Connection. The UI walks you through this order on purpose — Resend only shows the signing secret after you create a webhook with a URL.

Step 1 — Save API credentials

  1. Paste your Resend API key (re_...).
  2. Set a Primary From Address (verified sender on your domain).
  3. Click Save & continue.

Developer Inbox creates a connection id, seeds that address as a mailbox, and shows your webhook URL.

Step 2 — Create the webhook in Resend

  1. Copy the Webhook URL from Settings → Connection (includes your connection id).
  2. Open Resend Webhooks → Add Webhook.
  3. Paste the URL and subscribe to email.received.
  4. Save the webhook.
  5. Copy the Signing secret (whsec_...) Resend shows after save.

Step 3 — Save the signing secret

  1. Return to Settings → Connection.
  2. Paste the signing secret into Webhook Signing Secret.
  3. Click Finish setup.

Inbound mail will not verify until this secret is saved.

Multiple addresses (mailboxes)

One Resend connection can cover many addresses on your receiving domain (e.g. you@example.com and support@example.com):

  1. Open Settings → Mailboxes and add each address, or simply receive mail at a new address — inbound ingest auto-creates that mailbox and grants you access.
  2. Optionally mark one as Preferred (default Inbox/Sent filter and compose From).
  3. Use the mailbox switcher (sidebar on desktop; under search on mobile) to filter Inbox and Sent, or choose All mailboxes.
  4. Compose From is a list of addresses you can access (not free text).

Access is grant-based (today: you get direct access as the connection owner). The same model is designed for future teams and role-based sharing without changing how inbound mail is stored.


Step 5 — Send a test inbound email

  1. From any mailbox, send an email to an address on your receiving domain
    (e.g. you@your-receiving-domain.com).
  2. Within a few seconds you should see a new conversation in Inbox.
  3. Open the thread — From / To / Date and the body should appear.
  4. Reply from the thread. Replies send from the address that received the mail (not necessarily your preferred mailbox).

If nothing appears

  • Confirm the webhook URL matches Settings → Connection (and is publicly reachable by Resend)
  • Confirm the event type includes email.received
  • Confirm the signing secret matches
  • Check the mailbox switcher (new To addresses are created automatically on first inbound; refresh if the switcher was already open)
  • Check the app logs (in development you will see [webhook] lines)
  • In Resend, open the webhook and check delivery / retry history
  • Confirm MX for the receiving domain points at Resend

Step 6 — Send a new outbound email (optional)

  1. Click Compose in the inbox.
  2. From is a select of your accessible mailboxes (preferred / switcher selection is prefilled).
  3. Fill To, Subject, and body, then Send.
  4. A new conversation is created for that outbound message.

How it works (short)

External sender
    │
    ▼
Resend (MX / receiving)
    │  email.received webhook
    ▼
POST /api/webhooks/resend/:connectionId
    │  verify signature → fetch body via Receiving API
    ▼
Developer Inbox (conversations + messages)
    │
    ▼
You reply / compose in the UI
    │
    ▼
Resend Emails API → recipient

Notes:

  • Resend webhooks carry metadata only. Developer Inbox fetches HTML/text via the Receiving API.
  • One Resend API key / connection can cover multiple domains on that Resend account.
  • Domains are managed in Resend; Developer Inbox stores credentials, mailbox grants, and conversations — not DNS.
  • Settings is split into Overview, Connection (API key / webhook), and Mailboxes (addresses + preferred).

Security checklist

  • [ ] Never commit .env or API keys
  • [ ] Use ENCRYPTION_KEY so provider secrets are encrypted at rest
  • [ ] Keep webhook signing secret set and rotated if leaked
  • [ ] Prefer HTTPS webhook URLs Resend can reach (tunnel or production host)
  • [ ] Restrict Resend API key scope when possible

Ready to connect?

Sign in and open Settings → Connection to paste your Resend key.

Get started