Connect Resend for sending
Send newsletter issues and lifecycle email from your own domain, and let bounces, complaints, unsubscribes, opens and clicks come back into Ballad on their own.
Resend is how Ballad sends email for you. Connect it and your newsletter issues and lifecycle sequences go out from your own domain, under your own sending reputation, and the bounces, complaints, unsubscribes, opens and clicks come back into Ballad without you exporting anything.
Without it, Ballad still writes your issues; you copy them into whatever tool you already use. Everything below is optional in that case.
This takes about ten minutes, most of it waiting for DNS.
1. Verify a sending domain
In resend.com, add the domain you want to send from and
add the DNS records it gives you. Use a subdomain you don't send anything else
from, like mail.yourdomain.com or news.yourdomain.com, so a marketing issue
can never affect delivery of your product's own email.
Wait for Resend to mark the domain verified. Ballad checks this when you connect, and a broadcast to a list won't send from an unverified domain.
2. Make an API key
Under API Keys, create a key with full access. Ballad does more than send with it: it creates a list for each voice that sends, registers a webhook so results come back, and reads your domains to check the one you're sending from. A sending-only key fails at the first step.
Copy the key once. Resend won't show it again.
3. Add it as an email account
The key belongs to the workspace, so you add it once and every voice can send through it. In Ballad: Settings → Email → Add an email account (owners and administrators).
| Field | What to put in it |
|---|---|
| Provider | Resend. Others are listed as coming soon. |
| API key | The key from step 2. Leave blank later to keep the stored one. |
| Default from address | An address on the verified domain. |
| Default reply-to | Optional, if replies should land somewhere else. |
| Postal address | A real one. Anti-spam law in most countries requires it in the footer of a list email. |
Ballad checks the key, checks whether the from address's domain is verified, and registers one read-back webhook for the account. The account's row shows the key's last four characters, whether the domain is verified, which voices use it, and a warning if the webhook couldn't be registered. Send a test emails you from it. The first account is the default; Make default changes that.
4. Pick it for each voice that sends
Sending still goes out under whoever signs the issue. In Settings → Voices → the voice → Email tool, choose Resend, then:
| Field | What to put in it |
|---|---|
| Email account | Which workspace account this voice sends through. |
| From name | The name on the envelope. Blank uses the voice's name. |
| From address | Blank uses the account's. Set it to send as someone else on the same domain. |
| Reply-to | Blank uses the account's. |
| Send issues to | Everyone with consent, or one of your own segments. |
Save, and Ballad creates this voice's list on the account, then shows a pill with the address it's sending from, the number of recipients with consent, and a warning if the domain isn't verified.
The Set up your newsletter walkthrough in your Inbox does the same in one step: it offers the workspace's existing Resend account (a picker if there are several), or takes a new key, which is saved under Settings → Email so teammates' voices can send through it too.
What Ballad creates in your Resend account
- A segment named
<voice> list (Ballad)for each voice that sends. The people Ballad's own segments select are mirrored into it at send time, so Resend never holds a list Ballad hasn't applied consent to. - One webhook per account pointing back at Ballad, subscribed to
email.bounced,email.complained,email.opened,email.clicked,contact.updatedandsuppression.added.
Lists are reused if they already exist, so reconnecting a voice doesn't duplicate anything.
What comes back
| Event in Resend | What happens in Ballad |
|---|---|
| Opened, clicked | Recorded against the issue, and per person for a sequence step |
| Hard bounce | Consent withdrawn; sequences for that person stop |
| Spam complaint | Consent withdrawn, permanently |
| Unsubscribe | Consent withdrawn; they leave every segment that needs it |
That's why the webhook matters: without it Ballad would keep emailing someone who asked you to stop.
Rotating or disconnecting
To rotate a key, Edit the account in Settings → Email, paste the new key and save; the webhook moves to it. Disconnect on a voice's Email tool row stops that voice sending, and its issues go back to being pasted by hand; the account stays for other voices. Remove deletes an account from Ballad, and is refused while a voice still sends through it. Your Resend account, lists and history are untouched either way.
Troubleshooting
- "Resend rejected the key": the key is wrong, revoked, or not full access. Make a new one under resend.com/api-keys.
- "domain unverified": the from address is on a domain Resend hasn't verified yet. Check the DNS records; sending to a list will fail until it is.
- "no read-back webhook": the key couldn't create one, usually a permissions problem. Edit the account with a full-access key and save.
- Nobody receives an issue: check the recipient segment actually selects people with consent. The count is on the voice's Email tool row.
Next
- Newsletter and lifecycle email: issues, subscribers and sequences.
- People: where consent lives.
- Settings: the rest of the wiring.