Flowmails as a transactional email API: POST /api/email/send from your Worker
Cloudflare Workers can't talk to a traditional SMTP relay without a third-party bridge. Most teams bolt on SendGrid or Resend to fill that gap, which means a separate billing relationship, a separate dashboard, and a per-email fee. Flowmails removes the bolt-on: you POST to `https://<your-zone>.workers.dev/api/email/send` (or use the Flowmails SDK from any runtime), and the Worker in your Cloudflare account sends through Cloudflare Email Services directly. There is no SMTP relay, no per-email markup from Flowmails, and no shared sending IP from a SaaS — your domain sends from your Cloudflare zone. Transactional senders typically ship the first email in under an hour: connect the Cloudflare account, verify the zone, mint an API key, hit the SDK.
What hurts today
The transactional email api pain points
Cloudflare Workers can't natively SMTP — most teams bolt on SendGrid / Resend
Per-email pricing compounds fast at scale (10K+ transactional emails / month)
Hosted ESPs add a separate dashboard, separate billing, and a shared sending IP
How Flowmails answers
What you get instead
Single `POST /api/email/send` from any Workers-compatible runtime
Outbound sends go through Cloudflare Email Services — no SMTP relay, no per-email markup
Domain sends from your Cloudflare zone (DKIM / SPF / DMARC align automatically)
FAQ
Common questions from transactional email api
Other personas