What problem does it solve? Integrating transactional email into applications requires navigating Cloudflare Email Service's evolving APIs, domain onboarding, DNS authentication, and subtle differences between the Workers binding and REST API. This Skill provides up-to-date guidance, retrieval sources, and common-mistake fixes so agents and developers configure email correctly the first time. ## Core Features & Use Cases - Send emails from Workers or external apps: Use the send_email binding in Workers or the REST API from Node.js, Python, Go, or coding agents via wrangler CLI and MCP tools. - Receive and route inbound email: Implement the Workers email() handler to forward, reply, reject, or parse messages with postal-mime, including store-and-reply-later patterns with Durable Objects. - Deliverability and monitoring: Configure SPF/DKIM/DMARC, manage suppression lists, check sending quotas, and query GraphQL analytics datasets for delivery metrics. - Use Case: A developer asks an AI agent to add a welcome email to their Worker. The Skill ensures the domain is onboarded via wrangler email sending enable, the binding is declared in wrangler.jsonc, and both html and text bodies are sent. ## Quick Start Ask the agent to add a welcome email to your Cloudflare Worker using the send_email binding and verify the sending domain is onboarded.