agentsclimarketplace

Cloudflare email routing

Skill ComeOnOliver/skillshub/skills/secondsky/claude-skills/cloudflare-email-routing

đź§  The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install
npx -y skills add ComeOnOliver/skillshub --skill cloudflare-email-routing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Cloudflare Email Routing for receiving/sending emails via Workers. Use for email workers, forwarding, allowlists, or encountering Email Trigger errors, worker call failures, SPF issues.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

10.6 KB, ~2.4k tokens by cl100k_base, as published. Nobody here has run it

Cloudflare Email Routing

Status: Production Ready âś… | Last Verified: 2025-11-18


What Is Email Routing?

Two capabilities:

  1. Email Workers - Receive and process incoming emails (allowlists, forwarding, parsing)
  2. Send Email - Send emails from Workers to verified addresses

Both free and work together for complete email functionality.


Quick Start (10 Minutes)

Part 1: Enable Email Routing

Dashboard setup:

  1. Dashboard → Domain → Email → Email Routing
  2. Enable Email Routing → Add records and enable
  3. Create destination address:
  4. âś… Basic forwarding active

Part 2: Receiving Emails (Email Workers)

Install dependencies:

bun add [email protected] [email protected]

Create email worker:

// src/email.ts
import { EmailMessage } from 'cloudflare:email';
import PostalMime from 'postal-mime';

export default {
  async email(message, env, ctx) {
    const parser = new PostalMime.default();
    const email = await parser.parse(await new Response(message.raw).arrayBuffer());

    console.log('From:', message.from);
    console.log('Subject:', email.subject);

    // Forward to destination
    await message.forward('[email protected]');
  }
};

Configure wrangler.jsonc:

{
  "name": "email-worker",
  "main": "src/email.ts",
  "compatibility_date": "2025-10-11",
  "node_compat": true  // Required!
}

Deploy and connect:

bunx wrangler deploy

Dashboard → Email Workers → Create address → Select worker

Part 3: Sending Emails

Add send email binding:

{
  "name": "my-worker",
  "main": "src/index.ts",
  "compatibility_date": "2025-10-11",
  "send_email": [
    {
      "name": "SES",
      "destination_address": "[email protected]"
    }
  ]
}

Send from worker:

import { EmailMessage } from 'cloudflare:email';
import { createMimeMessage } from 'mimetext';

const msg = createMimeMessage();
msg.setSender({ name: 'App', addr: '[email protected]' });
msg.setRecipient('[email protected]');
msg.setSubject('Hello!');
msg.addMessage({
  contentType: 'text/plain',
  data: 'Email body here'
});

const message = new EmailMessage(
  '[email protected]',
  '[email protected]',
  msg.asRaw()
);

await env.SES.send(message);

Load references/setup-guide.md for complete walkthrough.


Critical Rules

Always Do âś…

  1. Enable node_compat: true for postal-mime
  2. Verify destination addresses before sending
  3. Parse with postal-mime for email content
  4. Use mimetext for creating emails
  5. Check message.from for allowlists
  6. Forward with message.forward() (not manual)
  7. Handle errors (email delivery can fail)
  8. Test with real emails (not just dashboard)
  9. Add MX records (automatic via dashboard)
  10. Log email activity for debugging

Never Do ❌

  1. Never skip node_compat (postal-mime requires it)
  2. Never send without verification (delivery fails)
  3. Never hardcode email addresses in public code
  4. Never skip parsing (raw email is hard to work with)
  5. Never ignore spam (implement allowlists/blocklists)
  6. Never exceed Gmail limits (500 emails/day to Gmail)
  7. Never skip error handling (emails can fail)
  8. Never modify DNS manually (use dashboard)
  9. Never expose email content in logs (PII)
  10. Never assume instant delivery (email is async)

Common Patterns

Allowlist

const allowlist = ['[email protected]'];

if (!allowlist.includes(message.from)) {
  message.setReject('Not on allowlist');
  return;
}

await message.forward('[email protected]');

Blocklist

const blocklist = ['[email protected]'];

if (blocklist.includes(message.from)) {
  message.setReject('Blocked');
  return;
}

await message.forward('[email protected]');

Reply to Email

const msg = createMimeMessage();
msg.setSender({ addr: '[email protected]' });
msg.setRecipient(message.from);
msg.setSubject(`Re: ${email.subject}`);
msg.addMessage({
  contentType: 'text/plain',
  data: 'Thanks for your email!'
});

const reply = new EmailMessage(
  '[email protected]',
  message.from,
  msg.asRaw()
);

await env.SES.send(reply);

Parse Attachments

const parser = new PostalMime.default();
const email = await parser.parse(await new Response(message.raw).arrayBuffer());

for (const attachment of email.attachments) {
  console.log('Filename:', attachment.filename);
  console.log('Type:', attachment.mimeType);
  console.log('Size:', attachment.content.byteLength);
}

Custom Routing Logic

async email(message, env, ctx) {
  const parser = new PostalMime.default();
  const email = await parser.parse(await new Response(message.raw).arrayBuffer());

  // Route based on subject
  if (email.subject.includes('[Support]')) {
    await message.forward('[email protected]');
  } else if (email.subject.includes('[Sales]')) {
    await message.forward('[email protected]');
  } else {
    await message.forward('[email protected]');
  }
}

Email Message Properties

Incoming Messages (ForwardableEmailMessage)

message.from        // Sender email
message.to          // Recipient email
message.headers     // Email headers
message.raw         // Raw email stream
message.rawSize     // Size in bytes

// Methods
message.forward(address)        // Forward to address
message.setReject(reason)       // Reject email

Parsed Email (PostalMime)

email.from          // { name, address }
email.to            // [{ name, address }]
email.subject       // Subject line
email.text          // Plain text body
email.html          // HTML body
email.attachments   // Array of attachments
email.headers       // All headers

Top 5 Errors Prevented

  1. "Email Trigger not available": Enable node_compat: true
  2. Destination not verified: Verify all send destinations
  3. Gmail rate limit: Max 500 emails/day to Gmail
  4. SPF permerror: Use dashboard to configure DNS
  5. Worker call failed: Check logs for parsing errors

Use Cases

Use Case 1: Support Ticket System

async email(message, env, ctx) {
  const parser = new PostalMime.default();
  const email = await parser.parse(await new Response(message.raw).arrayBuffer());

  // Create ticket in database
  await env.DB.prepare(
    'INSERT INTO tickets (email, subject, body, created_at) VALUES (?, ?, ?, ?)'
  ).bind(message.from, email.subject, email.text, Date.now()).run();

  // Send confirmation
  const msg = createMimeMessage();
  msg.setSender({ addr: '[email protected]' });
  msg.setRecipient(message.from);
  msg.setSubject('Ticket Created');
  msg.addMessage({
    contentType: 'text/plain',
    data: 'Your support ticket has been created.'
  });

  const confirmation = new EmailMessage(
    '[email protected]',
    message.from,
    msg.asRaw()
  );

  await env.SES.send(confirmation);
}

Use Case 2: Email Notifications

export default {
  async fetch(request, env, ctx) {
    // User signup
    const { email, name } = await request.json();

    const msg = createMimeMessage();
    msg.setSender({ name: 'App', addr: '[email protected]' });
    msg.setRecipient(email);
    msg.setSubject('Welcome!');
    msg.addMessage({
      contentType: 'text/html',
      data: `<h1>Welcome, ${name}!</h1>`
    });

    const message = new EmailMessage(
      '[email protected]',
      email,
      msg.asRaw()
    );

    await env.SES.send(message);

    return new Response('Welcome email sent!');
  }
};

Use Case 3: Email Forwarding with Filtering

async email(message, env, ctx) {
  const parser = new PostalMime.default();
  const email = await parser.parse(await new Response(message.raw).arrayBuffer());

  // Filter spam keywords
  const spamKeywords = ['viagra', 'lottery', 'prince'];
  const isSpam = spamKeywords.some(keyword =>
    email.subject.toLowerCase().includes(keyword) ||
    email.text.toLowerCase().includes(keyword)
  );

  if (isSpam) {
    message.setReject('Spam detected');
    return;
  }

  await message.forward('[email protected]');
}

When to Load References

Load references/setup-guide.md when:

  • First-time Email Routing setup
  • Configuring MX records
  • Setting up email workers
  • Configuring send email binding
  • Complete walkthrough needed

Using Bundled Resources

References (references/):

  • setup-guide.md - Complete setup walkthrough (enabling routing, email workers, send email)
  • common-errors.md - All 8 documented errors with solutions and prevention
  • dns-setup.md - MX records, SPF, DKIM configuration guide
  • local-development.md - Local testing and development patterns

Templates (templates/):

  • receive-basic.ts - Basic email receiving worker
  • receive-allowlist.ts - Email allowlist implementation
  • receive-blocklist.ts - Email blocklist implementation
  • receive-reply.ts - Auto-reply email worker
  • send-basic.ts - Basic send email example
  • send-notification.ts - Notification email pattern
  • wrangler-email.jsonc - Wrangler configuration for email routing

Official Documentation


Questions? Issues?

  1. Check references/setup-guide.md for complete setup
  2. Verify node_compat: true in wrangler.jsonc
  3. Confirm destination addresses verified
  4. Check logs for errors

What ships with it

62.9 KB alongside SKILL.md, 6 of them executable

GitHub clipped this repository’s file list, so this is at least 11 files and may be more.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.