Event-driven email automation on Amazon SES
Keep the $0.10/1,000 SES price. Ditch the Lambda glue code. FlowingMail is a startup-friendly automation builder that gives Amazon SES a visual workflow editor, contact database, template engine, and analytics - with a generous free tier and flat pricing instead of per-contact billing.
Why automate Amazon SES with FlowingMail
Amazon SES gives you the cheapest, most reliable delivery on the internet - but no UI for marketers, no templating, no segmentation, no workflows. FlowingMail adds the missing automation layer. Email returns $36–$45 per $1 spent industry-wide (DMA, 2026); on SES-rate pricing, that arbitrage is even better.
- Keep SES pricing ($0.10 per 1,000 emails) - zero markup on sending
- Generous free tier: 5 flows + 25,000 contacts - SES sandbox + FlowingMail Free covers early traffic
- No Lambda, SNS topics, or Step Functions to maintain
- Bring your existing verified domains and sending reputation - keep every bit of your SES rep
- Send from multiple SES regions (us-east-1, eu-west-1, ap-south-1) side-by-side
- Versioned REST API with OpenAPI spec - trigger flows from your code, no UI clicks required
Everything your SES setup was missing
A full marketing automation stack designed to sit on top of Amazon SES - not replace it.
Visual workflow editor
Drag triggers, conditions, delays, and send-action nodes onto a canvas. No YAML, no Step Function JSON.
Template engine with {{ variables }}
HTML and plain-text templates with live preview, fallback values, and built-in variables (first_name, unsubscribe_url, etc.).
Segmentation & groups
Target contacts by attributes, groups, or custom filters. Re-use the same segment across campaigns and flows.
Open, click, bounce, complaint analytics
Ingest SES event notifications (via SNS or FlowingMail's ingress) and visualize deliverability per campaign.
Sandbox & production-safe
We detect your SES account state and refuse to send to unverified addresses while you're still sandboxed.
Rate-aware scheduling
Respects your account's send quota and per-second rate limit so you never hit a ThrottlingException.
Connect SES in under 5 minutes
Three steps. No code.
Connect your AWS account
Paste an IAM user access key (or an assumed role ARN) with ses:SendEmail and ses:SendRawEmail permissions. Region pinned per sender.
Build your first flow
Pick a trigger (contact created, added to group, API event), branch on attributes, and drop send-email actions that reference your SES sender.
Turn it on
Activate the workflow. FlowingMail enqueues sends through SES, retries on transient failures, and records events in real time.
Keep your direct SES integration - or skip it entirely
You can trigger flows via the FlowingMail API and let us handle the SES call. Or use SES directly and let FlowingMail track events.
# $FLOW_ID and contactId come from the dashboard (flw_xxx / cnt_xxx).
POST https://api.flowingmail.com/v1/flows/{FLOW_ID}/trigger
Authorization: Bearer pk_xxx...
Content-Type: application/json
{
"contactId": "cnt_abc123",
"variables": { "plan": "pro" }
}Amazon SES automation - FAQ
No - FlowingMail sits on top of SES. Your emails still route through your own AWS account, using your verified domains and your SES sending quota. FlowingMail provides the workflow engine, contact database, templates, and analytics around it.
SES pricing is unchanged: $0.10 per 1,000 emails (plus data transfer). FlowingMail is billed separately - $0 Free, $14/mo Startup, or $42/mo Business (3 seats, extra seats available as an add-on). FlowingMail doesn't meter email volume and there is no per-email markup.
Yes. FlowingMail respects SES dedicated IP pools and will route through whichever IP pool your configuration set is bound to. IP warm-up can be managed with rate-limited workflows.
You can either forward SES event notifications (via SNS) to FlowingMail's ingress endpoint, or let FlowingMail poll the SES API directly. Hard bounces and complaints automatically suppress future sends to that contact.
If your SES account is sandboxed, FlowingMail blocks sends to unverified addresses and surfaces a clear warning in the dashboard. Once AWS lifts your limits, FlowingMail picks up the new quota automatically.
All SES-enabled regions. You can connect multiple senders (one per region) and route different flows to different regions for latency or compliance reasons.
Explore more
Build the same visual flows on Resend without changing providers.
Drop FlowingMail on top of your existing SendGrid account.
How email automation works - triggers, conditions, delays, and actions.
The drag-and-drop editor that powers every FlowingMail workflow.
Trigger receipts, password resets, and notifications from your app.
A ready-to-copy 5-step welcome flow for new signups.