Resend

Resend is Waypath’s outbound email channel — used for direct sends initiated by the Prospect buddy (“send this now”), NOT automated lifecycle sequences (those belong in Customer.io). Resend is BYOK per workspace: you bring your own API key and verify your own sending domain in your own Resend account, so deliverability reputation stays isolated from other Waypath tenants.

Setup

1. Add your API key

1. Open Settings → Integrations and find the Resend · Email card at the top.
2. Paste your Resend API key (starts with re_). Optional: pre-fill the default from and reply-to addresses.
3. Click Connect Resend. Waypath validates the key against GET /domains and persists it encrypted on your workspace.

2. Verify a sending domain

1. With the key connected, type your domain (e.g. mail.acme.com) and click Add.
2. Waypath calls Resend’s domain API and renders the three DNS records you need: MX, TXT (SPF), TXT (DKIM), plus an optional TXT (DMARC) record.
3. Copy each record into your DNS provider (Cloudflare, Hostinger, Route53, etc.). The copy-to-clipboard button is on the right of each row.
4. Click the Verify button next to the domain. Status flips from PENDING (amber) to VERIFIED (vermillion) once Resend sees the records — usually within a minute, sometimes longer depending on your DNS TTLs.

You can verify multiple domains and pick the From address per send — only verified domains can be used. Unverified sends are rejected with domain_not_verified before they hit Resend, so the operator gets a clear error instead of a silent deliverability problem.

Usage from the agent

The Prospect buddy has two outreach tools:

• draft_outreach({ prospectId }) — generates a signal-referenced email draft (subject + body) using the prospect’s exact pain signal. Show this to the operator first.
• send_outreach({ prospectId, from?, subject?, body? }) — sends via Resend. If from is omitted, the workspace’s default From email is used. The send is blocked unless the From domain is in your verified list.

Sample prompts:

"Draft outreach for Sarah Chen at Acme based on her hyper-signal."
"Send the draft we just made — use hello@mail.acme.com as the sender."

Behaviour notes

• No silent fallback. If your Resend key is missing/invalid or the From domain isn’t verified, the agent surfaces the error in chat — Waypath never silently routes through a shared sender.
• Idempotency. Each send carries an X-Idempotency-Key of waypath_<prospectId>_<recipient>_<subject>, so a retry won’t double-deliver.
• Touchpoints. Successful sends become Touchpoint nodes on the recipient’s Customer in your graph (channel: 'email'), feeding Intelligence correlation.

Resend vs Customer.io