Integrations

Email provider: Bring your own key, or don’t.

Enlist-managed sending needs zero configuration. Or connect your own Resend key and send on your own domain — Enlist still tracks delivery, opens, and clicks either way.

Reading delivery state
const { data } = await enlist.waitlists.listSignups(waitlistId, { limit: 1 });// data[0].email_status -> 'delivered' | 'opened' | 'clicked' | 'bounced' | …// Bring your own Resend key in Settings → Email://   API key            re_...          (resend.com/api-keys)//   Webhook secret      whsec_...       (optional — enables delivered/opened/clicked)
01

Zero-config default

New accounts start on "off" — nothing sends until you turn on managed email or connect your own key. Never a surprise send.

02

Your domain, your key

Add a Resend API key and a verified sending domain, and signup emails go out under your own name instead of Enlist’s.

03

Delivery state on the signup

Every signup carries an email_status field — sent, delivered, opened, clicked, or bounced — regardless of which provider sent it.

See the other integrations

REST, SDK, MCP, webhooks, and email — same key across all of them.