emdash-plugin-cloudflare-email

EmDash CMS email-provider plugin that delivers transactional email through the native Cloudflare Email Sending Workers binding. No API token required — auth happens via the binding.

Why this plugin instead of emdash-plugin-resend? If your EmDash Worker already runs on Cloudflare, this is one less third-party dependency, one less API key to manage, and one less HTTP hop.

Requires

• EmDash >= 0.5.0
• A Cloudflare Workers deployment (this is a trusted-mode plugin — see Caveats)
• A domain onboarded for Cloudflare Email Sending (see Setup)

Install

npm install emdash-plugin-cloudflare-email
# or pnpm add emdash-plugin-cloudflare-email

Setup

1. Onboard your domain to Cloudflare Email Sending (one-time)

npx wrangler email sending enable yourdomain.com

…or use the Cloudflare dashboard: Compute & AI → Email Service → Email Sending → Onboard Domain. This adds SPF / DKIM / DMARC records to your zone (DNS propagates in 5–15 min). To avoid touching SPF on a domain you already use for human mail (e.g. Google Workspace), onboard a subdomain like mail.yourdomain.com instead — the plugin's From address then becomes [email protected].

2. Add the binding to wrangler.jsonc

{
  "send_email": [
    { "name": "EMAIL" }
  ]
}

The binding name must be EMAIL in this release (configurable in a future version — see Roadmap).

3. Wire the plugin into astro.config.mjs

import { defineConfig } from 'astro/config'
import emdash from 'emdash/astro'
import cloudflareEmail from 'emdash-plugin-cloudflare-email'

export default defineConfig({
  integrations: [
    emdash({
      plugins: [cloudflareEmail()],
    }),
  ],
})

4. Configure the From address in the admin UI

Navigate to EmDash Admin → Cloudflare Email and enter your From address — for example Your App <[email protected]>. Save and use the Send Test Email button to verify delivery.

That's it. EmDash's email:deliver hook is now wired to the binding — invitations, magic links, password recovery, and any custom plugin emails will route through Cloudflare.

Caveats

• Trusted-mode only. The plugin uses the Workers send_email binding, which is only accessible to plugins running in the host Worker isolate (plugins: [] in astro.config.mjs). Sandboxed plugins (sandboxed: []) run in isolated V8 isolates without access to host bindings — install this plugin in trusted mode.
• Astro 6 + @astrojs/cloudflare v13+ is required, because the plugin uses import { env } from 'cloudflare:workers' to access the binding.
• Domain onboarding is irreducible. Cloudflare needs to know which domain you're allowed to send from before you can send. There's no way to skip step 1.

Roadmap

• binding option to override the binding name from EMAIL (e.g. cloudflareEmail({ binding: 'NOTIFY_EMAIL' }))
• Attachment support (currently only to/from/subject/html/text/cc/bcc/replyTo pass through)
• Restricted-binding support (e.g. allowed_sender_addresses)

PRs welcome.

License

MIT © Velvee