Resend - Nitrosend

Use your Resend account as the sending provider for Nitrosend campaigns, flows, and transactional email. See Email providers for how BYO sending works, plan requirements, and status semantics.

What you need

A Resend API key (from the Resend dashboard → API Keys). The key needs permission to read domains and send email — Nitrosend validates it against Resend's domains endpoint when testing the connection.

Connect from the dashboard

Go to Integrations in Nitrosend.
Choose Resend.
Paste your API key and save. Nitrosend tests the connection as part of saving a new integration.

Connect via MCP

{
  "operation": "configure",
  "provider": "resend",
  "api_key": "<RESEND_API_KEY>"
}

Warning

The MCP call stores the key without testing it. {"operation": "status"} reports stored configuration only — to actually test the credentials, run Test connection from the Resend integration page in the dashboard, or call POST /v1/my/integrations/{id}/test via the REST API.

Making it the active provider

If this is your first BYO provider, it becomes the brand's active email provider automatically. If you already had another provider connected, open the integration's page and choose Set as primary to switch sending to it.

Sending domains

After connecting, add your sending domain from Domains (or nitro_manage_domains). The DNS records returned come from Resend's domain verification.

Troubleshooting

"Resend API key is invalid" — the key was rejected by Resend. Generate a fresh key with full access (a send-only key can fail the domains check used by the connection test).
Rotated your key? Re-entering credentials resets this integration's verified domains to pending — re-verify them from Domains.