cloudflare-email-service

Send transactional emails via Cloudflare Workers bindings or REST API.

2|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/iadr-dev/colab --skill cloudflare-email-service-iadr-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudflare-email-service
Source: https://github.com/iadr-dev/colab/tree/main/skills/coding/cloudflare-skills/skills/cloudflare-email-service
Command: npx skills add https://github.com/iadr-dev/colab --skill cloudflare-email-service-iadr-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you send and route transactional emails on Cloudflare without getting stuck on setup, bindings, API field differences, or deliverability pitfalls.

Core Features & Use Cases

  • Send transactional email reliably using the Workers binding or the Email Sending REST API.
  • Receive and route inbound email by wiring an email() handler and using forwarding/reply patterns.
  • Improve deliverability and troubleshoot via SPF/DKIM/DMARC guidance, bounce/suppression concepts, and monitoring/analytics pointers.
  • Use with agents and MCP workflows to manage email endpoints and integrate email handling into an AI coding agent flow.

Quick Start

First, verify your sending domain is onboarded, then add the send_email binding and send an email from your Worker using env.EMAIL.send().

Frequently Asked Questions about cloudflare-email-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send transactional emails using Cloudflare Workers bindings?

To send transactional emails using Cloudflare Workers bindings, verify your sending domain is onboarded, add the send_email binding to your wrangler configuration, and call env.EMAIL.send() within your Worker script to dispatch messages.

What is the difference between the Cloudflare Email Sending REST API and Workers bindings?

The Cloudflare Email Sending REST API and Workers bindings handle outbound transactional email but use different field names and payload structures. The REST API is accessed via HTTP, while bindings use the env.EMAIL.send() method directly in Worker scripts.

Can I use Cloudflare Email Service with an AI coding agent via MCP?

Yes, you can integrate Cloudflare Email Service with AI coding agents via MCP and wrangler to manage email endpoints, route replies for support inboxes, and handle email workflows within the Agents SDK.

What deliverability requirements are needed for Cloudflare email sending?

Deliverability for Cloudflare email sending requires SPF, DKIM, and DMARC DNS configurations, verified forwarding destinations, and dual HTML and text payload formats to avoid bounces and suppression.

How do I process inbound email routing in a Cloudflare Worker?

Process inbound email routing in a Cloudflare Worker by wiring an email() handler function, then apply forwarding and reply patterns to route messages to support inboxes or other verified destinations.

Why are my Cloudflare transactional emails failing to send?

Cloudflare transactional emails fail when the sending domain is not onboarded, the wrangler send_email binding is misconfigured, REST API field names are incorrect, or payloads lack required HTML and text formats for deliverability.