SendGrid automation · Built for developers

Event-driven email automation on SendGrid

SendGrid's Marketing Campaigns is capped, clunky, and priced per-contact. FlowingMail is the startup-friendly automation builder for SendGrid - a visual canvas with triggers, delays, branches, and filters, running on the same SendGrid API key you already pay for. Flat pricing, generous free tier, zero markup.

Why FlowingMail

Why use FlowingMail with SendGrid

You already trust SendGrid's infrastructure. You don't need to trust their UI too. Keep the deliverability, swap the marketing layer. For scale: 41% of email orders come from the 2% of sends that are automated (Omnisend, 2026) - SendGrid's IPs + FlowingMail's automation is a much better-priced way to capture that.

Bring your own SendGrid API key - keep every IP and verified sender you already have
Startup-friendly flat pricing - no contact-based billing that balloons at scale
Generous free tier (5 flows, 25,000 contacts, 2 senders) to validate the migration
Event-driven: trigger flows from your code with a single POST request
Register multiple senders for multiple SendGrid API keys - useful for agencies and multi-tenant SaaS
Migrate off SendGrid Marketing Campaigns without rebuilding in a new ESP

Capabilities

Automation features that Marketing Campaigns lacks

Branching workflow canvas

True if/else branches, time-based delays, and nested conditions - not just linear drips.

Multi-attribute segmentation

Filter by plan, signup source, last-click-date, or custom attributes. Re-usable across flows and campaigns.

Dual HTML / text templates

Edit HTML and plain-text side-by-side with live preview. Variable interpolation with fallback values.

Campaign analytics

Sent / open / click / bounce / spam / unsubscribe rates, plus time-series charts per campaign.

CSV & API contact import

Bulk-import contacts, or push them from your app via the FlowingMail Contacts API.

Trigger from your code

One API call starts a flow. FlowingMail handles delays, branches, and SendGrid calls for you.

How it works

Hook up SendGrid in minutes

Add your SendGrid API key

Create an API key with Mail Send and Stats Read access, then paste it into FlowingMail's Senders page.

Design your flow

Triggers: contact created, added to group, REST event. Branch on attributes. Drop send actions bound to your SendGrid sender.

Ship it

Activate the flow. SendGrid delivers the mail, FlowingMail records every event via the Event Webhook.

Integration

Use the FlowingMail API, keep the SendGrid API key

You don't need to rewrite SendGrid send calls. Trigger FlowingMail flows from your code - the SendGrid send happens inside the workflow.

# $FLOW_ID is the flw_xxx ID from the dashboard.
curl -X POST "https://api.flowingmail.com/v1/flows/$FLOW_ID/trigger" \
  -H "Authorization: Bearer $FLOWINGMAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "contactId": "cnt_abc123",
    "variables": { "plan": "pro" }
  }'

FAQ

SendGrid automation - FAQ

No. FlowingMail uses your SendGrid account for delivery. Your IPs, domain authentication, and SendGrid dashboard stay exactly as they are. FlowingMail adds visual workflows, segmentation, and analytics on top.

Marketing Campaigns is tied to SendGrid's contact-based pricing and has a limited automation builder (linear drips only). FlowingMail has a full branching workflow canvas, flat pricing, and provider-portable templates.

Yes. Each SendGrid API key can be registered as its own FlowingMail sender, so agencies and multi-tenant SaaS teams can map Subusers (or separate SendGrid accounts) to FlowingMail senders and route different flows through different keys.

Dedicated IPs are respected - FlowingMail sends through the SendGrid API, which routes through whichever IP pool your account uses. For IP warm-up, use FlowingMail's Throttle node inside your flow to cap send rate.

Yes. Templates, contacts, and workflows are provider-agnostic. Add a new sender (SES or Resend), switch the send action's provider binding, and your flow runs on the new infrastructure.