What problem does it solve? Integrating transactional email into applications requires navigating domain onboarding, DNS authentication, binding configuration, and deliverability rules. This Skill provides up-to-date guidance for sending and receiving email through Cloudflare Email Service, preventing common configuration mistakes like missing bindings, unverified domains, and incorrect API field names. ## Core Features & Use Cases - Send emails from Workers: Configure the send_email binding in wrangler.jsonc and call env.EMAIL.send() with attachments, custom headers, and up to 50 recipients. - Send from any platform: Use the REST API with Bearer token authentication from Node.js, Python, Go, or coding agents via wrangler CLI and MCP tools. - Receive and route inbound email: Handle incoming messages with the Workers email() handler, parse MIME content with postal-mime, forward, reply, or store emails in Durable Objects for human-in-the-loop workflows. - Use Case: Add order confirmation emails to a Cloudflare Worker by onboarding your domain with wrangler email sending enable, adding the binding, and sending via env.EMAIL.send() with both HTML and text bodies. ## Quick Start Ask the agent to add transactional email sending to your Cloudflare Worker using the send_email binding and an onboarded domain.
