Email Sending
reflare.emailWorker gatewayCloudflare Email Sending
Connect the visual email editor to your own Cloudflare account, provision a Worker gateway, and keep the sending path small enough to reason about.
reflare.email setup notesCloudflare gateway preview
Your email path, visible.
Free usage limits
Cloudflare Email Sending works well when you want fewer provider handoffs: design the email in reflare.email, then send through a Worker that belongs to your own Cloudflare account. The app keeps the configuration explicit: provider, Worker URL, and gateway token.
The important part is trust. Tokens should be scoped, sender domains should be intentional, and saved credentials should be encrypted before they touch storage. This route is the compact map from blank setup to a first successful test send.
Setup path
The short route from token to Worker.
Step 1
Choose Cloudflare Worker in Configuration
Open the editor, click settings, and switch the provider to Cloudflare Worker so the send API knows which gateway to use.
Step 2
Paste a scoped Cloudflare API token
The app needs Account Settings Read, Zone Read, Workers Scripts Edit, and Workers AI Read/Edit for the selected account.
Step 3
Load accounts, zones, and sender domains
The resources endpoint reads the account data available to your token and lets you select which domains the Worker can send from.
Step 4
Provision the Worker gateway
The provision action deploys the Worker, creates a gateway bearer token, saves the Worker URL, and validates Workers AI access.
Provider config
The fields stay deliberately boring.
Boring configuration is easier to debug. The saved Cloudflare provider config has a small surface area, and each value maps to a concrete point in the send flow.
provider
cloudflare-worker
Switches sending away from Resend and through your Worker.
workerUrl
https://<worker>.<subdomain>.workers.dev
Public endpoint used by reflare.email when posting email payloads.
authToken
generated-gateway-token
Bearer token checked by the Worker before it accepts a send request.
Workers AI
10,000 neurons/day
Included free of cost for AI-powered checks. The paid Workers plan gives the gateway the best performance profile.
Debugging checklist
Start with the exact failure message.
401 while loading or saving config
Sign in again first. The config, resource, and provision routes require an authenticated user.
Token cannot list accounts or zones
Regenerate the API token with Account Settings Read and Zone Read for the Cloudflare account you want to use.
Worker provision succeeds but AI warns
Email sending can still work. Add Workers AI Read/Edit to the same account if you want AI validation to pass.
Mail does not send from the Worker
Check that the From address matches one of the selected sender domains and that Cloudflare Email Sending is enabled.
Resources