How It Works
- Connect a provider. Open Integrations in Brew and click the provider you want. OAuth integrations connect with one click; the rest take a credential or two.
- Use Brew like normal. Write, edit, and iterate on emails the way you always would.
- Send or export. From any email, click Send in the top right. Choose Send Email for direct delivery or Export Template to push the email into your connected ESP as a reusable template.
Send Through Your ESP
Push email templates from Brew into your existing ESP. Keep your sending infrastructure where it is, use Brew for creation.
Braze
Export templates to Braze for campaign management.
Brevo
Export templates to Brevo for email marketing.
Customer.io
Send emails through Customer.io.
HubSpot
Export templates to HubSpot Marketing Hub.
Iterable
Export templates to Iterable for campaigns and journeys.
Klaviyo
Export Brew emails to Klaviyo as CODE templates.
Mailchimp
Export templates to Mailchimp.
Mailgun
Export templates to Mailgun.
Mailjet
Export templates to Mailjet.
OneSignal
Export templates to OneSignal.
Postmark
Export templates to Postmark.
SendGrid
Export templates to SendGrid.
OAuth (one-click): Brevo, HubSpot, Klaviyo, Mailchimp.Credential-based: Braze, Customer.io, Iterable, Mailgun, Mailjet, OneSignal, Postmark, SendGrid.
Trigger Automations from Events
Connect auth, commerce, and billing platforms so their events fire Brew automations. Welcome new signups, drip dunning on failed payments, recover abandoned carts, notify on role changes, without writing webhook glue code.How Event Triggers Work
Every event-source integration in this section follows the same flow once connected:1
Brew gives you a unique webhook URL
Each connection mints its own server-issued URL scoped to your brand. You paste this URL into the provider’s dashboard so they know where to send events.
2
Brew signature-verifies every webhook
Brew checks the signing secret on every delivery before doing anything else. Tampered or replayed events are rejected with no automation fired.
3
Published automations fire and your audience auto-syncs
For every verified event Brew (1) starts every published automation whose trigger matches and (2) upserts the contact into your audience with provider-namespaced custom fields (
clerk_user_id, stripe_subscription_status, shopify_last_order_at, etc.) you can use in filters and merge tags. Connecting the provider auto-provisions every supported event. There’s no per-event enable step. To stop a specific event from firing, unpublish its bound automation.Each provider page below walks through the exact connect flow, the supported events, and the personalization variables you can use inside emails.
Clerk
User signups, org changes, paid subscriptions, and waitlist entries.
RevenueCat
In-app purchases + subscriptions across App Store, Play Store, Stripe, and Web Billing.
Shopify
Customer, order, checkout, cart, and fulfillment events.
Stripe
Subscriptions, invoices, checkouts, refunds, quotes.
Stytch
Consumer (B2C) and B2B auth events, user lifecycle, member changes, organization activity.
Supabase
auth.users events including derived email-confirmed, password-changed, and ban / unban signals.
WorkOS
Enterprise auth: SSO users, password resets, organizations, SCIM directory sync.
Productivity and Data
Bring designs and signals into Brew, or chat with your AI assistant from where you work.
Figma
Paste a Figma frame URL into chat. Brew converts the design to a responsive email.
Slack
Mention @brew in any channel or thread to create and edit emails.
Typeform
Pull survey responses into Brew to inform emails. Coming soon.
AI Agents
Brew is built to be operated by AI agents. Any agent that can call an HTTP API can use Brew to design, send, and trigger emails.Use Brew with AI agents
Generic guide for any agent. Claude, OpenClaw, Replit, Viktor, and others.
Lovable
Worked example: send transactional emails from Lovable apps via Supabase Edge Functions.
Have an integration you need? Let us know and we’ll prioritize it.