Cloudflare Email Sending

Cloudflare Email Sending is a transactional-only sender. Waitlyze can use it for subscriber verification messages. Cloudflare prohibits marketing and bulk email, so broadcasts and marketing automations continue to use the workspace or waitlist's Resend sender.

Connect a workspace accountCopy Anchor Link

1. In Cloudflare Email Service, onboard the sender domain. The zone must belong to the Cloudflare account that owns the API token.
2. Create an API token with Email Sending: Edit for that account. The account owner should scope it as narrowly as Cloudflare allows and treat it like a password.
3. In Waitlyze, open Settings → Integrations → Cloudflare Email Sending. Enter the Cloudflare account ID, token, and an address on the onboarded domain.
4. Send a test message to your Waitlyze account email. The saved token is encrypted and never shown again.

The token is used through Cloudflare's Email Sending REST API for transactional signup confirmation only. It is not used for broadcasts, automations, or other campaign sends. Disconnecting the integration returns transactional messages to your workspace Resend sender when one is connected, otherwise to the Waitlyze Cloudflare sender.

Sender setup and costsCopy Anchor Link

Email Sending must be enabled and its DNS records verified in Cloudflare before a sender works. Cloudflare adds separate bounce-processing records; they do not replace the root MX, SPF, or DKIM records used by Email Routing.

Cloudflare's documented Workers Paid plan starts at $5/month and includes a sending allowance, with usage charges beyond the included amount. Cloudflare budget alerts are informational and do not cap or stop charges. Waitlyze does not enable paid Cloudflare services automatically; the account owner must explicitly accept usage-based billing.

Bounces, complaints, and suppressionCopy Anchor Link

Cloudflare Email Sending publishes delivery lifecycle events (including message.bounced and message.complained) through event subscriptions to a Cloudflare Queue. Waitlyze consumes the waitlyze-email-events queue and applies permanent bounces and complaints to the sending workspace's suppression list, so those addresses stop receiving campaign email - the same behavior as the Resend webhook path. Configure the subscription on your sending domain (Cloudflare dashboard → Email Service → event subscriptions, or the API) targeting that queue; events for other statuses are acknowledged and ignored.

When to use Resend insteadCopy Anchor Link

Use Resend for opted-in subscriber broadcasts and marketing automations. Cloudflare Email Service terms do not allow marketing or bulk campaigns, even when a workspace supplies its own Cloudflare token. See Resend for sender and suppression setup.