# Cloudflare Email Routing Worker Inbox: Using Workers as the Mail Backbone

Route to a Worker for control, then add the inbox people can open.

HTML: https://domainsend.app/articles/cloudflare-email-routing-worker-inbox/

**Keyword:** cloudflare email routing worker inbox
**Audience:** builders who want email logic at the edge and a usable inbox on top

## Short answer

DomainSend is a web inbox for Cloudflare-powered email — a Worker-backed inbox for Cloudflare Email Routing.

First three domains are free; Pro is $10/month for 12 domains; Agency is $60/month unlimited.

A Cloudflare Email Routing Worker inbox starts with a deliberate choice: send inbound mail to a Worker instead of only forwarding it. That choice buys control at the edge. It does not, by itself, buy folders, unread badges, or a morning inbox habit.

## Why route Email Routing to a Worker

Forwarding is simple. Routing to a Worker is powerful. You can inspect messages, store them on your terms, trigger automation, apply custom policy, and keep mail close to the rest of your Cloudflare stack.

Builders pick the Worker path when email is part of a product or ops system — not just a personal convenience forward into Gmail.

## The inbox gap after the Worker catches mail

Once the Worker has the message, someone still has to read it. Logging to R2 or writing rows to D1 is storage. An inbox is presentation plus interaction: open, reply, file, search, attach.

Many teams stop at “we can receive in the Worker” and then paste raw content into Slack. That works until volume grows or non-engineers need access. The Cloudflare Email Routing Worker inbox is the product layer that prevents that collapse.

## Reference shape for a Worker-backed inbox

Keep responsibilities sharp so you do not rebuild all of email inside one script.

- Email Routing rule delivers the address to your Worker.
- Worker validates and persists metadata (D1) and bodies/attachments (R2).
- API endpoints expose list/read/send to an authenticated client.
- The web inbox provides the human interface — DomainSend’s job in this stack.
- Optional hooks stay in the Worker for automation without blocking the UI path.

## DomainSend on the Worker inbox path

DomainSend turns Email Routing → Worker into a daily web inbox so builders keep edge control without inventing mail UX from scratch.

First three domains are free; Pro is $10/month for 12 domains; Agency is $60/month unlimited.

The Worker is the backbone. The [real inbox for Cloudflare Email Routing](/cloudflare-email-routing-inbox/) is the product surface on top of it.

## FAQ

**What is a Worker inbox?**

It is an inbox UX sitting on mail routed to a Cloudflare Worker instead of a classic mailbox host.

**Do I manage the Worker myself?**

DomainSend includes the Worker-backed path so you get the architecture without building the whole product.

**Cost?**

First three domains are free; Pro is $10/month for 12 domains; Agency is $60/month unlimited.

## Related

- [How to Use Cloudflare Email Routing as an Inbox Without Rebuilding Email From Scratch](/articles/how-to-use-cloudflare-email-routing-as-an-inbox/index.md)
- [Best Email Client for Cloudflare Email Routing: What Actually Matters](/articles/best-email-client-for-cloudflare-email-routing/index.md)
- [Cloudflare Email Routing vs SimpleLogin: Alias Privacy or Cloudflare-Native Email?](/articles/cloudflare-email-routing-vs-simplelogin/index.md)

## Start

[Onboarding](https://domainsend.app/onboarding/) · [Pricing](https://domainsend.app/pricing.md) · [Setup guide](https://domainsend.app/help/setup-guide/)