Back to catalog / Integrations
Cloudflare Email Service: verify domain and sending path first
Distinguish Worker-binding, REST, agent reply, and inbound-routing workflows.
Skills
Route by intent: Workers `send_email` (no API key), Agents `onEmail()/replyToEmail()`, external REST bearer token, or inbound `email()` handler. Check Wrangler types, domain enablement, `wrangler.jsonc`, and whether `postal-mime` is needed. Retrieve current limits, API, and compliance docs. Enabling a domain/routing changes the account; sending reaches real recipients, so confirm scope and authorization. Keep tokens and message contents out of logs.
Permissions
Prerequisites
- Implement or troubleshoot Cloudflare Email Sending/Routing, inbound parsing, domain setup, and deliverability.
Permissions
- May configure domains/bindings, send or process mail; REST API requires a bearer token.
Limitations
Check domain enablement, `send_email` binding, and parsing dependency; retrieve current permissions/limits/pricing. Sending contacts recipients, so confirm content and list.
Pinned upstream source
- Repository
- cloudflare/skills
- File path
- skills/cloudflare-email-service/SKILL.md
- Pinned commit
53395984c3ea1925d00fce03b266112302f050e6- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
Workers `send_email` binding · `wrangler email sending` / `email routing` · Email Sending REST API · Workers `email()` handler
Main topic
Turn ecommerce campaign materials into a reviewable weekly brief