What the Resend connection does
PubOps can use Resend for live email delivery, contact and suppression sync, and delivery events such as opens, clicks, bounces, and complaints.
Before you connect
- Create an account with Resend and verify your sending domain there.
- Have an API key and a sender address on that verified domain ready. Keep the key private.
- If contact synchronization should be limited to a Resend segment, have that segment’s ID ready. PubOps sends to its eligible-recipient set.
Connect Resend in PubOps
As an owner or admin, open Settings → Email destinations, connect Resend, and enter the API key and verified sender.
Deployment defaults for self-hosted administrators
These settings belong in the service environment, not in issue content:
RESEND_API_KEY=re_xxxxxxxxxxxx # Optional: limit contact sync to one Resend segment RESEND_SEGMENT_ID=xxxxxxxx-xxxx-xxxx EMAIL_FROM="PubOps <hello@yourdomain.com>" RESEND_WEBHOOK_SECRET=whsec_xxxxxxxx
Test before sending
Run the connection test, then preview contact sync. The preview does not change data. If the test fails, check that the key is active, has the required access, and points to an existing optional segment. A connection test is not proof of inbox delivery: use a test send and inspect the received email before a live issue send.
When audience data is missing
Your service administrator needs a Resend webhook pointing to /api/webhooks/resend on the PubOps service, with its signing secret configured. Supported audience events include opens, clicks, bounces, and complaints. Check Activity & delivery → Webhooks for received events. A connected destination alone does not mean measurement is working.