David

<p>EdgeMail intercepts WordPress outbound email (wp_mail) and sends it via your Cloudflare Worker endpoint instead of using the default PHP mailer.</p>
<h4>Features</h4>
<ul>
<li><strong>Cloudflare Integration</strong>: Send emails through your Cloudflare Worker using the Email Service API</li>
<li><strong>Safe Fallback</strong>: Automatically falls back to default WordPress email if Worker fails or plugin is not configured</li>
<li><strong>Email Logging</strong>: Track all email attempts with status, HTTP codes, and responses</li>
<li><strong>Easy Configuration</strong>: Simple settings page with Worker URL, API token, and default From fields</li>
<li><strong>Test Email</strong>: Send test emails to verify your configuration</li>
<li><strong>WooCommerce Status</strong>: View recent email logs and configuration status in WooCommerce <span aria-hidden="true" class="wp-exclude-emoji">→</span> Status</li>
<li><strong>Zero Downtime</strong>: Unconfigured installations continue to work normally</li>
</ul>
<h4>Cloudflare Email Service</h4>
<p>This plugin is designed to work with Cloudflare’s Email Service, announced in September 2025. Your Cloudflare Worker endpoint should handle the email sending using the <code>env.SEND_EMAIL.send()</code> binding.</p>
<h4>Installation</h4>
<ol>
<li>Upload the plugin to the <code>/wp-content/plugins/</code> directory</li>
<li>Activate the plugin through the ‘Plugins’ menu in WordPress</li>
<li>Go to Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> EdgeMail in the WordPress admin</li>
<li>Configure your Worker URL, API token, and default From fields</li>
<li>Send a test email to verify your configuration</li>
</ol>
<h4>Configuration</h4>
<p>In the EdgeMail settings page, you’ll need to provide:</p>
<ul>
<li><strong>Worker URL</strong>: Your Cloudflare Worker endpoint (e.g., https://your-worker.your-subdomain.workers.dev)</li>
<li><strong>API Token</strong>: Shared secret for authenticating with your Worker</li>
<li><strong>Default From Name</strong>: Default sender name for emails</li>
<li><strong>Default From Email</strong>: Default sender email (must be verified in Cloudflare Email Service)</li>
</ul>
<h4>Limitations</h4>
<ul>
<li>Attachments are not supported in v1</li>
<li>Requires WordPress 5.7+ (uses pre_wp_mail filter)</li>
</ul>
<h3>Privacy Policy</h3>
<p>This plugin may collect the following data:</p>
<ul>
<li>Email delivery logs (recipient email addresses, subject lines, delivery status, timestamps) are stored in the database for troubleshooting and compliance purposes</li>
<li>Worker endpoint URL and API token are stored in wp_options for plugin functionality</li>
<li>No user data is sent to third parties except for email delivery through your configured Cloudflare Worker endpoint</li>
</ul>
<p>All data is stored locally on your WordPress installation. This plugin does not track users or send data to external analytics services.</p>


EdgeMail

Replace WordPress transactional email with Cloudflare Worker endpoint integration.

icyapril

manatarms

patrickmeenan

jwineman

thellimist

s1lviu

<p>Combine the <a href="https://github.com/cloudflare/worker-examples/tree/master/examples/edge-cache-html/WordPress%20Plugin/cloudflare-page-cache" rel="nofollow ugc">Cloudflare Page Cache Plugin</a> in order to offer edge-cached HTML content on the Cloudflare CDN for non-authenticated users with the power of Cloudflare Workers.<br />
In this manner, the static content will be delivered from the Cloudflare large network and consists in big improvements, including TTFB and loading time.<br />
This plugin has the advantage of automation of Worker creation via APIs.</p>


Edge Cache HTML via Cloudflare Workers

Caching pages on Cloudflare CDN with the power of Workers, auto-purging when content changes.

EdgeMail vs Edge Cache HTML via Cloudflare Workers