Cloudflare Email Service has entered public beta, enabling applications and agents to send emails at scale. The platform provides bidirectional email communication through Email Routing for inbound messages and Email Sending for outbound delivery, allowing developers to build email-native workflows without external dependencies.
Email Sending, which graduated from private beta today, allows developers to send transactional emails directly from Cloudflare Workers using a native binding. The service automatically configures SPF, DKIM, and DMARC authentication records, ensuring emails reach inboxes rather than spam folders. Emails are delivered with low latency across Cloudflare’s global network.
Cloudflare Email Service for Agent Workflows
The Agents SDK now includes a first-class onEmail hook that enables agents to receive messages, process them asynchronously, and send replies independently. Unlike chatbots that respond immediately or not at all, agents can spend hours processing data, checking multiple systems, and then reply with complete answers. They can schedule follow-ups, escalate edge cases, and operate on their own timeline.
Each agent receives its own identity from a single domain. Address-based routing directs [email protected] to a support agent instance and [email protected] to a sales instance. Sub-addressing enables routing to different agent namespaces. State persists across emails through Durable Objects, allowing agents to maintain conversation history and context without separate databases.
Security and Integration Features
Secure reply routing is built into the platform using HMAC-SHA256 signing of routing headers. This prevents attackers from forging headers to route emails to arbitrary agent instances, addressing a security gap in competing email-for-agents solutions. The artificial intelligence infrastructure integrates with Cloudflare’s broader developer platform, including Workers AI for classification and R2 for attachment storage.
Email Service is accessible to agents running anywhere, not just on Cloudflare infrastructure. Three integrations make the service available to agents in local environments, containers, or external clouds. The Cloudflare MCP server gives agents access to Email endpoints through simple prompts. The Wrangler CLI solves context window problems by allowing agents to discover capabilities on demand through help commands.
Developer Tools and Reference Applications
Cloudflare is publishing a Cloudflare Email Service skill that provides agents with complete guidance on configuring Workers bindings, sending emails via REST API or SDKs, handling inbound email with Email Routing, building with the Agents SDK, and managing email through Wrangler CLI or MCP. The skill covers deliverability best practices and techniques for crafting transactional emails that avoid spam filters.
The company is open-sourcing Agentic Inbox, a reference application demonstrating how to build a full email client with agent automations. The application includes conversation threading, email rendering, attachment storage, and automated replies. It features a dedicated MCP server allowing external agents to draft emails for human review before sending. Developers can deploy Agentic Inbox with a single click to get a complete inbox, email client, and agent for managing emails.
Expanding Agent Capabilities Across Platforms
During private beta, developers built customer support agents, invoice processing pipelines, account verification flows, and multi-agent workflows on top of email. The pattern demonstrated that email is becoming a core interface for agents, requiring infrastructure purpose-built for the channel. Cloudflare Email Service addresses this need by combining email routing, sending, and the Agents SDK into a unified platform.
The public beta release includes Email Sending binding available from Workers and the Agents SDK, a new Email MCP server, Wrangler CLI email commands, and skills for coding agents. These tools enable developers to build production-ready email agents without rebuilding common inbound-classify-reply pipelines. The reference application provides a starting point that teams can fork, extend, and customize for their specific workflows.
