cloudflare-email-service

Add a send_email binding to wrangler.jsonc, then call env.EMAIL.send() with to, from, subject, and both html and text bodies. The from address must use a domain onboarded to Email Sending 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 access subject, text, and attachments.

Use the Workers binding for code running inside Workers since it needs no API keys. Use the REST API with a Bearer token for external applications in Node.js, Go, or Python, or when HTTP integration is explicitly required.

message.raw is a single-use ReadableStream, so a second read returns nothing. Buffer it first with new Response(message.raw).arrayBuffer() and reuse the buffer for parsing, forwarding, or storage.

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

message.forward() only works with verified destination addresses. Verify the destination first in the Dashboard or by running wrangler email routing addresses create before forwarding.