Cloudflare announces the private beta of its new Email Sending service, a capability integrated directly into Cloudflare Workers, which, along with the existing Email Routing, forms the unified Cloudflare Email Service. This new offering aims to simplify transactional email management for developers by eliminating the burden of managing external email infrastructure. Key features include deep integration with Workers via bindings for secure, direct sending; automatic configuration of necessary DNS records (SPF, DKIM, DMARC) for improved deliverability; and global low-latency delivery. The service supports sending rich HTML emails using frameworks like React Email. The combined Email Service allows developers to build complete email workflows, handling both outbound sending and inbound message processing via Workers AI for tasks like summarization and ticket creation. Email Sending will require a paid Workers subscription, with pricing based on messages sent.
Cloudflare Launches Email Service: Simplified Transactional Email via Workers
0:00 Introduction: Email is a critical but often annoying burden for developers, used for signups, notifications, and increasingly, AI agent workflows.
0:17 Announcement: Cloudflare launches the private beta of Email Sending, allowing transactional emails to be sent directly from Cloudflare Workers.
0:26 Unified Service: Email Sending joins Email Routing to form the new Cloudflare Email Service, providing a single developer experience for all email needs.
0:30 Simple Worker Integration: Sending an email is achieved by adding an Email binding to a Worker and calling the send method, exemplified by a simple "Hello World" example.
0:44 Deliverability Focus: The service emphasizes reliability and fast time-to-inbox by tightly integrating with DNS to automatically configure crucial verification records (SPF, DKIM, DMARC).
1:00 Global Delivery: As a global Cloudflare service, it promises low-latency delivery worldwide without managing separate regional servers.
1:18 Secure Workflow: Developers use the Email binding to securely send emails without managing external API keys or secrets.
1:25 Full Workflow Support: The service facilitates end-to-end workflows, allowing Workers to process incoming mail, store attachments in R2, and use local emulation during development via wrangler.
1:46 Rich HTML Support: Developers can use existing frameworks like React Email; the service accepts rendered HTML content in the send method.
2:10 Inbound/Outbound Synergy: Combining Sending with existing Email Routing allows for powerful inbound processing (e.g., summarizing emails with Workers AI or creating support tickets).
2:40 Closing the Loop: A user emailing support can trigger a Worker to receive, process, create a ticket externally, and use Email Sending to confirm the ticket number back to the user.
2:55 Pricing and Availability: Email Sending requires a paid Workers subscription, with billing based on messages sent. The private beta begins in November; Email Routing remains free and available now.