Resend Automations integration
Pipeline hands a lead.qualified event to Resend Automations with the full sequence pre-rendered. Each step calls back to AgentGate before dispatch to catch leads that went stale.
Dispatch is intentionally thin. We do not write our own ESP — we hand qualified leads to Resend Automations and let the Automation engine drive the sequence. Resend handles the SMTP, the bounce tracking, the click tracking (off by default per our GDPR posture), and the reply detection.
Handoff payload
The hand-off is a single lead.qualified event with the lead id, the campaign id, all pre-rendered drafts (subject, body, html, text), the AgentGate decision payload, and the chainlog_event_id. Resend stores the drafts and triggers them on a schedule we control.
Per-step AgentGate re-check
Between the lead.qualified event and a given dispatch step, hours or days may pass. The recipient may have unsubscribed via an earlier sender, the company may have gone bust, the signal may have expired. Each step calls back to AgentGate immediately before dispatch — if the lead has gone stale, the step is skipped and a Chainlog event records the skip.
Two free MCP tools surface this pipeline inside Cursor or Claude Desktop — no key required.