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 sending and receiving email on Cloudflare with correct configuration from the start. ## 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 external app: Use the REST API with Bearer token authentication from Node.js, Python, Go, or curl, with correct address/reply_to field naming. - Receive and route inbound email: Implement the Workers email() handler to forward, reply, reject, or parse messages with postal-mime, including Agents SDK integration. - Deliverability and monitoring: Manage suppression lists, check sending quotas, and query GraphQL analytics for delivery rates and bounce causes. - Use Case: You need your Cloudflare Worker to send a password-reset email. This Skill walks you through onboarding your domain, adding the binding, and sending with both HTML and text bodies to avoid spam folders. ## Quick Start Ask the agent to add email sending to your Cloudflare Worker using the send_email binding and onboard your domain with wrangler.
