cloudflare-email-service

Add a send_email binding to wrangler.jsonc with { "send_email": [{ "name": "EMAIL" }] }, then call env.EMAIL.send() with to, from, subject, html, and text fields. The from domain must be onboarded first via wrangler email sending enable.

Export an email() handler from your Worker and create a routing rule pointing addresses to it. Buffer message.raw once with new Response(message.raw).arrayBuffer(), then parse it with postal-mime to extract subject, text, and attachments.

The Workers binding uses email in the from object, replyTo in camelCase, and returns a messageId. The REST API uses address, reply_to in snake_case, returns delivered/permanent_bounces/queued arrays, and requires a Bearer API token.

No. Cloudflare Email Service is restricted to transactional email triggered by user actions, such as signups, password resets, and order confirmations. Marketing newsletters and bulk campaigns require a dedicated marketing email platform.

This error means the from domain has not been onboarded to Email Sending. Run npx wrangler email sending enable yourdomain.com or onboard the domain in the Cloudflare Dashboard, which auto-configures SPF and DKIM records.

The message.raw stream is single-use, so a second read returns empty. Buffer it first with const raw = await new Response(message.raw).arrayBuffer(), then reuse the buffer for parsing or forwarding.