Mail flow · Cloudflare email guide

Cloudflare Email Routing Send Email: From Receiving Mail to a Complete Workflow

Receive is only half the loop. Complete the workflow with compose and send.

Lo-fi illustration of a full receive-and-send email loop

“Cloudflare Email Routing send email” is the search people make when inbound finally works and outbound still feels unfinished. Routing decides where received mail goes. Sending is a separate path — and a usable compose UI is the third piece most setups forget.

Short answer: FlareMail is a web inbox for Cloudflare-powered email — turning inbound routing into a complete email workflow.

FREE for your first domain

Cloudflare email inbox in your browser. Additional domains are $9.99/mo.

FREE 1st domain · $9.99/mo more
Lo-fi corkboard illustration with EDGE_ROUTER.EXE pinned above Email for Cloudflare domains

Inbound routing does not equal outbound send

Email Routing is built around destinations for mail that arrives at your domain. You can forward, drop, or hand messages to a Worker. That does not automatically give you a From address, SPF/DKIM alignment story, or a compose window your team trusts.

Cloudflare’s email sending capabilities (including Worker bindings in Email Service docs) cover the infrastructure side of outbound. They still leave you needing somewhere to write the reply, attach a file, and see what you sent.

Circular loop of receive, read, compose, send
A complete Cloudflare email workflow closes the loop back to the person writing replies.

The four steps of a complete Cloudflare mail loop

Treat receive and send as one workflow, not two unrelated projects.

Illustrated send button on a grainy zine poster
If sending feels bolted on, the client layer is usually what is missing.

Where sending setups usually stall

Teams often wire inbound in an afternoon, then spend weeks on outbound because the pieces live in different places: DNS records in Cloudflare, sending credentials or Worker config elsewhere, and “just use Gmail SMTP” as the temporary fix that becomes permanent.

The stall is rarely “Cloudflare cannot send.” It is “nobody owns the product surface where sending feels like email.” That surface is the client.

How FlareMail closes the send loop

FlareMail is built for the full daily loop on Cloudflare-powered email: read, organize, compose, and send in one web inbox. You are not jumping from a forward destination to a separate SMTP tool every time someone needs a reply.

If you searched for Cloudflare Email Routing send email because receive already works, FlareMail is the compose-and-send layer that makes the workflow feel finished. FREE for your first domain; additional domains are $9.99/mo.

Ready for a real Cloudflare inbox?

FlareMail is FREE for your first domain. Additional domains are $9.99/mo.

FREE 1st domain · $9.99/mo more
Lo-fi corkboard illustration with EDGE_ROUTER.EXE pinned above Email for Cloudflare domains

Sources and context

FAQ

Can Cloudflare Email Routing send email by itself?

Routing is inbound-focused. Sending is configured separately and still needs a usable compose experience.

What does FlareMail add?

The daily loop: read, organize, compose, send, and keep conversations in one inbox.

Is FlareMail subscription-based?

Your first domain is free. Additional domains are $9.99/mo.

FREE for your first domain. Web inbox for Cloudflare Email Routing — additional domains are $9.99/mo.

FREE 1st domain · $9.99/mo more