SkillsCloudflare & infrastructure › Cloudflare Email Service
cloudflare-email-service

Cloudflare Email Service

Send and receive transactional email straight from Cloudflare Workers — the “your order shipped” kind of automated email, plus the SPF/DKIM/DMARC setup that keeps it out of spam. A building block if we ever want a connector or Worker to email on its own.

Claude Code only
How to use it
Tell Claude you want a Worker (or agent) to send/receive email and it sets up the binding or REST call, the domain onboarding via wrangler, and deliverability basics, all grounded in the current docs. Claude Code only: it runs wrangler and edits a Workers project. Note: this is the Cloudflare developer service — our team’s everyday email still goes through the Gmail connector.
How to invoke / keep it on
Say you want to add email to a Worker in Claude Code and it auto-loads, even for “just add email” — it carries the fiddly config details.
20 powerful examples for Melinda Maria
Copy, tweak, make them yours. Just describe the task — Claude loads the skill automatically.
01"If we wanted an internal Worker to email #ops a daily “low inventory” alert built from ShipHero data, show me how to send that email from Cloudflare — and whether Gmail would be simpler."
02"Walk me through onboarding our sending domain with wrangler and getting SPF/DKIM/DMARC right so automated emails don’t land in spam."
03"Explain the difference between the Workers email binding and the REST API, and which one a small alerting Worker should use."
04"Set up an incoming-email handler so a future connector could receive and parse a vendor’s order-confirmation emails."
05"Help me send a weekly automated “connector health” digest email summarizing which MCP connectors are green, from a Worker."
06"Explain DKIM signing in plain English and how to confirm ours is actually working before we rely on automated email."
07"Show me how to attach a generated CSV (like a NuORDER reorder list) to an outbound email from a Worker."
08"Set up an alert email that fires only when the loudcrowd nightly sync fails, so we’re not spammed when everything’s fine."
09"Compare Cloudflare Email, the Gmail connector, and Klaviyo for a specific use case, and tell me which fits when."
10"Walk me through verifying domain ownership so Cloudflare will let a Worker send as @melindamaria.com."
11"Help me write a clean, on-brand plain-text body for an automated ops alert so it reads like Melinda Maria, not a robot."
12"Show me how to rate-limit outbound email from a Worker so a bug can’t accidentally send hundreds of alerts."
13"Explain DMARC policy (none vs quarantine vs reject) and the safe order to tighten it without losing legitimate mail."
14"Set up an incoming-email route that drops parsed shipping notifications into a connector’s store for later querying."
15"Help me test sending email from a Worker without spamming real inboxes, using a safe test recipient first."
16"Show me how to handle a bounce or failure response from the email send so the Worker logs it instead of silently dropping it."
17"Explain whether transactional email from Cloudflare could power a simple back-in-stock note, or whether that’s really a Klaviyo job."
18"Walk me through keeping the sending key secret with wrangler secret put so the email credential is never in the code."
19"Help me forward a copy of every automated alert to an archive address so we have a record of what the Worker sent."
20"Draft a plain-English explainer for the team on the difference between “transactional” and “marketing” email and which tool we use for each."
← Back to Cloudflare & infrastructure
Powered by our people. Amplified by AI. Ready-to-run playbooks for every team.