✉️ Connect Resend

Resend is the newest service on the Sending screen and the simplest to set up. If you are comfortable adding a few DNS records and want to be sending in about ten minutes, it is a great place to start.

Resend only sends from domains you have verified with it. That keeps your delivery clean, and it means the From email on your emails must be on that domain.

What you need before you start:

• A Resend account, created on the Resend website.
• Access to the DNS for your sending domain.
• About ten minutes.

Where to find it:

In ResultsAiX Mailer open Delivery, then Sending, click + Add Sender and choose Resend in the Provider dropdown. Its four step checklist and one API Key box appear.

Step 1. Verify your domain at Resend:

1. In your Resend dashboard, add your domain, for example yoursite.com.
2. Add the DNS records it gives you at your DNS host. There are only a few, covering DKIM and the return path.
3. Wait for the domain to show as verified. It is usually quick.

Step 2. Create an API key:

In Resend, create an API key with sending access, and copy it.

Step 3. Fill in the form:

The Resend part of the form has one box.

• API Key: the key from step 2, shown as dots.

Then fill in the rest of the form:

• Display name: for example Resend.
• From name and From email: an address on the verified domain, for example Anna at Leafwise and anna@yoursite.com.
• Reply-To: for example hello@yoursite.com.
• Daily limit (0 = unlimited): your plan's allowance for a day, so a big send paces itself.
• Priority (lower = preferred): 10 for your main service, or 20 for a backup.
• Active: leave it ticked.

Click Save Sender, then click Test on the new row. A green "Test sent via Resend" box means you are ready.

Step 4. Set up the webhook:

1. On the Sending screen, click Copy URL next to Resend in the Bounce & complaint webhook box.
2. In Resend, open Webhooks and add an endpoint with the URL.
3. Choose the email bounced and email complained events.

Resend says whether each bounce is permanent or temporary, and the Mailer suppresses permanent bounces and logs temporary ones. Complaints are suppressed straight away.

A real example:

Leafwise Gardening runs a small spring planting list from a second site. Anna verifies yoursite.com on the Resend website, creates a key with sending access, and adds a connection called Resend with From email anna@yoursite.com, Daily limit 3,000 and Priority 10. The test passes in under a minute, and the webhook goes in straight after.

Tips:

• Use one key per website, named after the site, so you can replace one without touching the others.
• Switch on Warm up for a new account before a large broadcast. See Warmup: Drip A Big Send Through A Cold Server.
• Your own domain authentication still does the heavy lifting. See Deliverability: SPF, DKIM And DMARC.
• If you outgrow the plan, add a second connection and share the load. See SMTP Rotation: Spread Sends Across Many Connections.

If something does not look right:

• If the test fails and mentions the domain or the From address, check that the From email is on the verified domain and that Resend shows the domain as verified, not pending.
• If the test fails with a key or permission message, create a key with sending access and paste it again.
• If a broadcast uses a different From from your test, check the broadcast's sender profile. Every From you send with must be on a domain Resend has verified.