cloudflare-email-routing
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.
What this skill does
# 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: - Custom: `[email protected]` - Destination: Your email - Verify via email 4. ✅ Basic forwarding active ### Part 2: Receiving Emails (Email Workers) **Install dependencies:** ```bash bun add [email protected] [email protected] ``` **Create email worker:** ```typescript // 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:** ```jsonc { "name": "email-worker", "main": "src/email.ts", "compatibility_date": "2025-10-11", "node_compat": true // Required! } ``` **Deploy and connect:** ```bash bunx wrangler deploy ``` Dashboard → Email Workers → **Create address** → Select worker ### Part 3: Sending Emails **Add send email binding:** ```jsonc { "name": "my-worker", "main": "src/index.ts", "compatibility_date": "2025-10-11", "send_email": [ { "name": "SES", "destination_address": "[email protected]" } ] } ``` **Send from worker:** ```typescript 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 ```typescript const allowlist = ['[email protected]']; if (!allowlist.includes(message.from)) { message.setReject('Not on allowlist'); return; } await message.forward('[email protected]'); ``` ### Blocklist ```typescript const blocklist = ['[email protected]']; if (blocklist.includes(message.from)) { message.setReject('Blocked'); return; } await message.forward('[email protected]'); ``` ### Reply to Email ```typescript 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 ```typescript 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 ```typescript 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) ```typescript 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) ```typescript 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 ```typescript 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 ```typescript 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 ```typescript async email(message, env, ctx) { const parser = new PostalMime.default(); const email = await parser.parse(await ne
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.