> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brew.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect Brew to the ESPs, auth providers, commerce platforms, design tools, and AI agents you already run, and see what each connection does.

Brew integrates with the tools you already use. Send emails through your existing ESP, pull design context from Figma, kick off automations from auth + commerce + billing events, or let any AI agent operate Brew through its API.

## How It Works

1. **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.
2. **Use Brew like normal.** Write, edit, and iterate on emails the way you always would.
3. **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.

<CardGroup cols={3}>
  <Card title="Braze" img="https://cdn.brew.new/integrations/integration-braze-icon.png" href="/integrations/export/braze">
    Export templates to Braze for campaign management.
  </Card>

  <Card title="Brevo" img="https://cdn.brew.new/integrations/integration-brevo-icon.png" href="/integrations/export/brevo">
    Export templates to Brevo for email marketing.
  </Card>

  <Card title="Customer.io" img="https://cdn.brew.new/integrations/integration-customerio-icon.png" href="/integrations/export/customerio">
    Send emails through Customer.io. Template export is manual.
  </Card>

  <Card title="HubSpot" img="https://cdn.brew.new/integrations/integration-hubspot-icon.png" href="/integrations/export/hubspot">
    Export templates to HubSpot Marketing Hub.
  </Card>

  <Card title="Iterable" img="https://cdn.brew.new/integrations/integration-iterable-icon.png" href="/integrations/export/iterable">
    Export templates to Iterable for campaigns and journeys.
  </Card>

  <Card title="Klaviyo" img="https://cdn.brew.new/integrations/integration-klaviyo-icon.png" href="/integrations/export/klaviyo">
    Export Brew emails to Klaviyo as CODE templates.
  </Card>

  <Card title="Mailchimp" img="https://cdn.brew.new/integrations/integration-mailchimp-icon.png" href="/integrations/export/mailchimp">
    Export templates to Mailchimp.
  </Card>

  <Card title="Mailgun" img="https://cdn.brew.new/integrations/integration-mailgun-icon.png" href="/integrations/export/mailgun">
    Export templates to Mailgun.
  </Card>

  <Card title="Mailjet" img="https://cdn.brew.new/integrations/integration-mailjet-icon.png" href="/integrations/export/mailjet">
    Export templates to Mailjet.
  </Card>

  <Card title="OneSignal" img="https://cdn.brew.new/integrations/integration-onesignal-icon.png" href="/integrations/export/onesignal">
    Export templates to OneSignal.
  </Card>

  <Card title="Postmark" img="https://cdn.brew.new/integrations/integration-postmark-icon.png" href="/integrations/export/postmark">
    Export templates to Postmark.
  </Card>

  <Card title="SendGrid" img="https://cdn.brew.new/integrations/integration-sendgrid-icon.png" href="/integrations/export/sendgrid">
    Export templates to SendGrid.
  </Card>
</CardGroup>

<Info>
  **OAuth (one-click):** Brevo, HubSpot, Klaviyo, Mailchimp.

  **Credential-based:** Braze, Customer.io, Iterable, Mailgun, Mailjet, OneSignal, Postmark, SendGrid.

  **[Customer.io](/integrations/export/customerio) is the exception to template export.** It delivers Brew emails through your account rather than pushing templates into it. To reuse a Brew email as a Customer.io template, export the HTML and upload it to Design Studio.
</Info>

## 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:

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Published automations fire and your audience auto-syncs">
    For every verified event Brew (1) starts every **Live** [automation](/create-emails/automations) whose trigger matches and (2) upserts the contact into your [audience](/audience/add-contacts) 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.
  </Step>
</Steps>

<Info>
  Each provider page below walks through the exact connect flow, the supported events, and the personalization variables you can use inside emails.
</Info>

<CardGroup cols={3}>
  <Card title="Clerk" img="https://cdn.brew.new/integrations/integration-clerk-icon.png" href="/integrations/import/clerk">
    User signups, org changes, paid subscriptions, and waitlist entries.
  </Card>

  <Card title="RevenueCat" img="https://cdn.brew.new/integrations/integration-revenuecat-icon.png" href="/integrations/import/revenuecat">
    In-app purchases + subscriptions across App Store, Play Store, Stripe, and Web Billing.
  </Card>

  <Card title="Shopify" img="https://cdn.brew.new/integrations/integration-shopify-icon.png" href="/integrations/import/shopify">
    Customer, order, checkout, cart, and fulfillment events.
  </Card>

  <Card title="Stripe" img="https://cdn.brew.new/integrations/integration-stripe-icon.png" href="/integrations/import/stripe">
    Subscriptions, invoices, checkouts, refunds, quotes.
  </Card>

  <Card title="Stytch" img="https://cdn.brew.new/integrations/integration-stytch-icon.png" href="/integrations/import/stytch">
    Consumer (B2C) and B2B auth events, user lifecycle, member changes, organization activity.
  </Card>

  <Card title="Supabase" img="https://cdn.brew.new/integrations/integration-supabase-icon.png" href="/integrations/import/supabase">
    `auth.users` events including derived email-confirmed, password-changed, and ban / unban signals.
  </Card>

  <Card title="WorkOS" img="https://cdn.brew.new/integrations/integration-workos-icon.png" href="/integrations/import/workos">
    Enterprise auth: SSO users, password resets, organizations, SCIM directory sync.
  </Card>
</CardGroup>

## Productivity and Data

Bring designs and signals into Brew, or chat with your AI assistant from where you work.

<CardGroup cols={3}>
  <Card title="Figma" img="https://cdn.brew.new/integrations/integration-figma-icon.png" href="/integrations/import/figma">
    Paste a Figma frame URL into chat. Brew converts the design to a responsive email.
  </Card>

  <Card title="Slack" img="https://cdn.brew.new/integrations/integration-slack-icon.png" href="/integrations/import/slack">
    Mention @brew in any channel or thread to create and edit emails. In development.
  </Card>

  <Card title="Typeform" img="https://cdn.brew.new/integrations/integration-typeform-icon.png" href="/integrations/import/typeform">
    Pull survey responses into Brew to inform emails. Coming soon.
  </Card>
</CardGroup>

## 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.

<CardGroup cols={3}>
  <Card title="Brew MCP Server" icon="plug" href="/api-reference/mcp/overview">
    One URL connects Claude, ChatGPT, Cursor, or Codex to the full Brew toolset. No integration code.
  </Card>

  <Card title="Build Brew Into Your App" icon="code" href="/integrations/ai-agents/use-brew-with-ai-agents">
    Patterns for agents that ship email as part of what they build.
  </Card>

  <Card title="Lovable" icon="heart" href="/integrations/ai-tools/lovable">
    Worked example: trigger Brew automations from Lovable apps via Supabase Edge Functions.
  </Card>
</CardGroup>

<Info>
  Have an integration you need? [Let us know](mailto:founders@brew.new) and we'll prioritize it.
</Info>
