What problem does it solve? Adding transactional email to an application involves confusing setup steps: domain onboarding, SPF/DKIM records, choosing between a Workers binding and a REST API, and avoiding subtle field-name differences that cause failed sends. This Skill guides you through Cloudflare Email Service configuration, sending, receiving, and deliverability monitoring with current, retrieval-first documentation. ## Core Features & Use Cases - Send emails from Workers or external apps: Use the send_email binding in a Worker, the REST API from Node.js/Python/Go, or the Agents SDK onEmail()/replyToEmail() methods for AI agents. - Receive and route inbound email: Implement the email() handler to forward, reply, reject, or parse messages with postal-mime, including a store-and-reply-later Durable Object pattern. - Manage deliverability: Handle bounces, suppression lists, sending limits, and GraphQL analytics for delivery monitoring. - Use Case: A coding agent needs to add a "deployment complete" notification email to a CI pipeline. The Skill provides the exact wrangler command to onboard the domain and the correct REST API payload with address (not email) in the from object. ## Quick Start Ask the agent to add email sending to your Cloudflare Worker using the send_email binding and onboard your domain with wrangler.
