Use case · Newsletter

Ship newsletters on your own provider, without per-subscriber billing

Event-driven email automation for developers, creators, and founders. Flat pricing, a generous free tier, and a proper automation builder - so your newsletter doesn't cost more than your hosting bill at 10,000 readers.

Why FlowingMail

Why run your newsletter on FlowingMail

Email drives $36–$45 in revenue for every $1 spent (DMA, 2026). The only thing that punishes that ROI is an ESP charging you per subscriber as your list grows. FlowingMail separates the tools from the delivery.

  • Flat monthly pricing - your list can 10x without your bill changing
  • Bring your own email provider: Resend, SendGrid, Mailgun, Amazon SES, or SMTP
  • Generous free tier - 5 flows, 25,000 contacts, 2 senders, zero credit card
  • Automation builder with branching (not just linear drips)
  • Trigger from your CMS: new-post webhook → auto-send to subscribers
  • API-first - trigger, segment, and publish from your own code
Capabilities

Three newsletter patterns FlowingMail covers on day one

Scheduled broadcasts

Weekly / bi-weekly / monthly sends on a cron trigger. Timezone-aware: ship 8am to every subscriber, wherever they are.

On-publish sends

Your CMS (Ghost, Sanity, Contentlayer, Notion) fires a webhook when a post goes live - FlowingMail renders the template and sends.

Welcome + drip for new subscribers

Contact Created trigger → welcome email → 3-email back-catalog drip → exit into the main weekly broadcast.

Segmented newsletters

Filter by interest tags, plan, or engagement - send the 'deep-dive' edition only to subscribers who clicked the last one.

Per-issue analytics

Open / click / unsubscribe rates per issue, plus a long-term engagement score per subscriber.

Plain-text-first templates

Best deliverability + highest reply rates come from plain text. FlowingMail's editor encourages it.

How it works

From CMS post to inbox in three steps

01

Connect a provider

Paste your SES / Resend / SendGrid / Mailgun API key. Verify your sending domain.

02

Design the flow

Trigger on webhook or schedule → filter by segment → render template with post content → send.

03

Publish and watch

Each new post auto-sends. Opens and clicks stream back in real-time.

Integration

Trigger the newsletter from your CMS

Your CMS fires a single webhook on publish - FlowingMail handles the render, segmentation, and send.

# Wire your CMS "post-published" webhook to a serverless function that
# creates a campaign targeting your newsletter group and schedules it.

# 1. Create the campaign
curl -X POST https://api.flowingmail.com/v1/campaigns \
  -H "Authorization: Bearer $FLOWINGMAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Weekly issue - What we shipped",
    "subject": "What we shipped this week",
    "templateId": "tmp_newsletter",
    "senderId": "snd_resend",
    "audience": [
      { "type": "groups", "groupNames": ["newsletter"] }
    ],
    "variableValues": {
      "post_title": "What we shipped this week",
      "post_url": "https://blog.acme.com/shipped",
      "post_excerpt": "A short summary..."
    }
  }'
FAQ

Newsletter automation - FAQ

Yes. Tag paid subscribers as a group, filter sends by group, and optionally branch content by tier. Pair with Stripe / Lemon Squeezy for subscription management - forward the webhook to FlowingMail to toggle paid status automatically.

FlowingMail injects a standards-compliant List-Unsubscribe header + a one-click unsubscribe link. Unsubscribed contacts are added to a global suppression list and synced to your provider.

Yes. CSV import handles lists of any size. For lists over 100k, use the streaming Contacts API to batch-import with rate limiting.

Deliverability is mostly a function of your sending domain (SPF / DKIM / DMARC) and your provider's reputation - both of which you own when you connect your own provider. FlowingMail handles List-Unsubscribe, feedback loops, and suppression list sync on your behalf.

Templates are HTML + plain-text. If your CMS exports Markdown, convert it to HTML at publish time (most CMSes do this) and pass it as a template variable. A utility for MDX → inlined-HTML is on the roadmap.

FlowingMail Startup ($14/mo) + Amazon SES at $0.10 per 1,000 emails = roughly $29/month for 100k sends. Same volume on Mailchimp is $270+/mo. The arbitrage is why we built FlowingMail.

Explore more

Ship your first automation today

Connect a provider, trigger your first flow, keep every cent of your email ROI

Event-driven email automation for developers. Startup-friendly pricing, generous free tier, and zero markup on sending. No credit card required.