Resend

Resend is a transactional email service. It's the bit of an app that sends the emails users actually expect: a sign-up confirmation, a password reset link, a receipt after a purchase. If your app has accounts or payments, it almost certainly needs to send email, and Resend is how Appsanic does it.

Connect it once in Dashboard → Connectors → Resend and every project in your account can send mail through it. Connecting requires a paid plan.

What you get by connecting it

With Resend connected and Account access switched on, the agent can set up sending inside your Resend account using server-side tools (it never sees your admin keys):

• Registers your sending domain so mail goes out from your own address rather than a shared sandbox one.
• Hands you the DNS records to add - the SPF, DKIM, and related entries Resend needs you to publish at your domain registrar so your mail is trusted and not flagged as spam.
• Provisions a scoped sending key for your app to use, kept narrow to the one job of sending.

Every one of these actions lands in the Activity feed at the bottom of the connector page, with secrets stripped, so you can see exactly what was done and when. The scoped key is never bundled into the app people download - see Keys and security.

Connecting it

You connect Resend by pasting your credentials into the connector page. There's no one-click OAuth for Resend (that exists only for Supabase and Stripe).

You'll need:

• An API key - starts with re_, and is server-side only. Find it in the Resend dashboard under API Keys.
• A from address (optional) - the address your app sends from, once your domain is registered.

Then:

1. Open Dashboard → Connectors → Resend.
2. Paste the API key (and the from address if you have one).
3. Switch on Account access if you want the agent to register your domain and provision the scoped key for you. Left off, the agent writes the sending code plus step-by-step setup instructions and you run them yourself.

Saved secrets are shown as dots - the stored key never round-trips back to the browser, so you see that a key exists, encrypted, not the value. Use Test connection any time to re-check the saved credentials against the live service, and Disconnect (behind a confirmation) to remove them.

Keys and security

Resend's API key is a secret key - anyone holding it can send mail on your account - so it must never be bundled into an app people download. Resend is also one of the three account access connectors (alongside Supabase and Stripe): with the toggle on, the agent acts inside your account through server-side tools and provisions a scoped sending key, rather than asking you to embed anything sensitive in the client.

The credentials you save are encrypted at rest with AES-256-GCM. The browser only ever sees that a secret exists; the AI never sees a decrypted secret; and the agent never asks for a key in chat. If you paste a key into chat anyway, it refuses to use it and points you back to the connector page (and any key that's touched a chat should be rotated).

Useful links

• Resend documentation: https://resend.com/docs
• Appsanic guide: Sending Email

Next

Read Sending Email for how to actually send confirmations, resets, and receipts from your app.