Cloudflare Email Routing Workers

Build, deploy, and test serverless email-driven applications and AI agents directly on Cloudflare Email Routing using email(message, env, ctx), postal-mime, and cloudflare:email.

Whether you are building a lightweight email forwarder/reject rule, an AI customer support auto-responder with strict loop protection, or an inbound invoice parser archiving PDF attachments to Cloudflare R2, Cloudflare Email Workers process inbound messages at edge latency without maintaining dedicated mail servers.

When to Use

• Inbound email processing: You are intercepting incoming emails on your custom domain via Cloudflare's email(message, env, ctx) handler.
• MIME parsing in V8 isolates: You need to extract text bodies, HTML, sender metadata, and attachments using the isolate-native postal-mime parser.
• Outbound transactional auto-replies: You are sending replies or notifications via the send_email binding (EmailMessage from cloudflare:email or mimetext).
• RFC 5322 conversation threading: You are preserving email threads in Gmail, Outlook, and Apple Mail using In-Reply-To, References, and Re: subject prefixes.
• Attachment extraction to R2: You are archiving incoming PDF/image attachments directly to Cloudflare R2 object storage.
• Automated triage & ticketing: You are piping email inquiries into AI classification models, webhooks, or databases (D1, KV).

When Not to Use