Connect Resend to SiteOps
Resend is an email sending service: you verify a domain once, and from then on tools can send email from it through one API key. No campaign builder, no audience manager — just reliable delivery from an address that is actually yours.
That is exactly the piece SiteOps needs. SiteOps drafts and schedules emails — a monthly note to readers, an announcement tied to a calendar event — but it does not run its own mail servers. Connect Resend and those scheduled emails have a way out into the world, sent from your domain, with sent, opened and clicked counts flowing back.
The setup has two halves, and both live in plain sight: verify your domain in Resend by pasting a few DNS records, then tell SiteOps the key and the from address. Until both halves exist, scheduled emails wait safely as drafts — nothing is ever sent half-configured.
Set it up, step by step
0 of 7 done
- Domains
- Add domain
- API keys
- Create API key
The key's whole journey — one vendor page to one SiteOps field - Settings
- Resend
- Save
Let an agent do it
An agent with access to your DNS can add Resend's SPF and DKIM records for you.
Add the Resend domain verification records to my DNS.
1. I added <my sending domain> in Resend and its domains page shows a short list of DNS records — SPF and DKIM TXT records, plus an MX for the return path. Here they are exactly as displayed: <each record: type, host, value>.
2. Open the DNS zone for the domain at <my DNS host, e.g. Cloudflare or the registrar> and add each record with the exact type, host and value. Watch for the host trap: if the DNS host auto-appends the domain, enter only the prefix (for example resend._domainkey), so the host does not end up doubled.
3. Check each record resolves: dig TXT <host> +short for the SPF and DKIM entries, dig MX <host> +short for the return-path record.
4. Tell me when they resolve so I can press Verify in Resend.Creating the Resend account, pressing Verify, creating the API key and pasting it into SiteOps stay with you.
If something does not work
- The domain is stuck on Not verified
- Almost always a copying issue. Open your DNS and compare each record against what Resend shows — type, host and value must match exactly, and some registrars append your domain to the host on their own. Fixed records can still take a few hours to be seen everywhere; press Verify again after a break.
- The key saved but my emails still sit as drafts
- The from address is the missing half. Open the Email section in SiteOps settings and set the sender name and address — the address has to be on the domain you verified. The draft's note says exactly which half the gate is waiting on.
- My first emails landed in spam
- New sending domains start with no reputation. Keep SPF and DKIM verified, send steadily rather than in bursts, write like a person instead of a flyer, and use a reply-to that a human actually reads. Reputation builds over a few weeks of normal sending.
- Can I send from my Gmail address instead?
- No — and you would not want to. Mail sent from a free address through an outside service fails the checks inboxes run, so it goes straight to spam. Verifying a domain you own is the whole trick to landing in the inbox.
- I connected both Resend and Postmark — which one sends?
- Whichever one the 'Sends go through' picker in SiteOps Settings names — that choice is yours, not a hidden rule. Both can stay connected without stepping on each other; only the picked one sends, and you can switch it any time in the Email section.