Can I attach metadata (account id, plan) to inbound messages?

Yes — your Worker runs on every inbound message. Read the to-address, look up the routing rule in your D1, enrich with whatever context your support backend needs, and write it back before forwarding to the inbox or webhook.

How does Flowmails handle abuse / spam reporting?

Same as any other inbound: the `abuse@` mailbox is a normal inbox row, the webhook fires your pipeline, and your Worker can flag the sender domain or add headers for downstream filtering.

Can we share access to an inbox without sharing Cloudflare credentials?

Yes. The Flowmails dashboard is per-account and you can invite teammates with scoped roles. They see the inbox UI without ever touching the Cloudflare API token.

Self-hosted · CFFlowmails

Runtime v0.1Login

For SaaS support teams

Self-hosted on Cloudflare

Flowmails for SaaS support teams: shared inboxes that wire straight into your CRM

Support teams usually want a multi-mailbox setup — `support@`, `billing@`, `abuse@` — with events streaming into the ticketing system. Most hosted ESPs handle this with mailbox aliases, but the data lives in their database and you can't easily query it from your own backend. Flowmails handles the routing and the inbox in your D1; webhooks stream inbound events into your backend in real time, and your Worker can attach metadata (account id, plan tier) to each message before it lands. The CRM integration becomes a single subscription to a webhook endpoint, not a daily CSV export.

Start free See pricing

What hurts today

The saas support teams pain points

Hosted ESPs treat mailboxes as opaque — there's no SQL access to the inbox

Webhooks fire but the inbox copy lives elsewhere, so you can't correlate

Per-mailbox pricing scales worse than per-domain pricing as you grow

How Flowmails answers

What you get instead

Full inbox is queryable SQL — `SELECT * FROM email WHERE mailbox = 'support@'`

Webhooks stream with consistent schema, so your CRM gets clean payloads

Add a new shared mailbox (e.g. `press@`, `legal@`) by appending a routing rule — no plan change

FAQ

Common questions from saas support teams

Other personas

All Flowmails for pages

For Indie developers For Agencies and studios For Privacy-sensitive products For Transactional email API