Integration

Resend

Confirms alert email delivery can work from a verified sender.

Resend makes transactional email simple, but launch alerts still fail when the API key is valid while the sender domain is unverified. PreFlight verifies API reachability, confirms sender-domain readiness, and records safe delivery errors without logging message secrets.

Requirements

<IntegrationRequirements items={[ "Resend API key with send permissions", "Verified sender domain in Resend", "Launch alert recipient address for delivery tests", ]} />

What PreFlight checks

| Probe | What it proves | | --- | --- | | API reachability | The API key can authenticate against Resend. | | Sender domain readiness | The configured domain is verified before delivery tests run. | | Alert delivery | A safe test message can be sent to the launch alert recipient. | | Error handling | Delivery failures are recorded without logging API keys or message content. |

Failure guidance

| Symptom | Fix | | --- | --- | | Invalid API key | Create a restricted key in Resend dedicated to launch monitoring. | | Domain unverified | Complete DNS verification for your sending domain in Resend. | | Delivery rejected | Confirm the from-address uses the verified domain and the recipient accepts mail. | | Wrong environment | Use the production Resend key and domain your app will send from at launch. |

Dashboard setup

Open Integrations → Resend in your PreFlight project. Paste the Resend API key and verified sender domain. Add the launch alert recipient email for delivery verification. Run Pre-Flight Check and confirm domain and delivery probes pass.

<RelatedLinks links={[ { href: "/docs/integrations/postmark", title: "Postmark", description: "Server token and sender signature verification." }, { href: "/docs/integrations/sendgrid", title: "SendGrid", description: "Alternative transactional email and event webhooks." }, { href: "https://resend.com/docs", title: "Resend documentation", description: "API keys, domains, and sending reference." }, ]} />