Connect Stripe to Brevo in two minutes.
Real-time triggers from Stripe, ready-made actions in Brevo. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Stripe.
- Charge FailedWebhook
- Checkout CompletedWebhook
- New CustomerWebhook
- New DisputeWebhook
- Invoice PaidWebhook
Workflows do something in Brevo, instantly.
- Add Contact to ListAPI
- Create ContactAPI
- Delete ContactAPI
- Get ContactAPI
- List ContactsAPI
- List Brevo ListsAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Stripe, do it in Brevo.
10 Stripe triggers wired to 9 Brevo actions. Most-used pairing: Charge Failed → Add Contact to List.
Or fire it the other way around.
5 Brevo triggers wired to 31 Stripe actions downstream.
See Brevo → Stripe →Common Stripe → Brevo workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Fires when a new customer is created in Stripe. Use to mirror to your CRM, send a welcome email, or enrich the customer record before first charge.
Connect Stripe and Brevo in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Stripe and Brevo
Open Tiny Command, authorize Stripe and Brevo once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Stripe trigger
Drop the Stripe → Charge Failed trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/stripe.trigger-charge-failed - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Brevo action
Drop the Brevo → Add Contact to List action below it. Map fields from the Stripe payload into the Brevo inputs.
brevo.add-contact-to-list - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Stripe + Brevo.
How long does it take to connect Stripe and Brevo on Tiny Command?
Is the Stripe ↔ Brevo integration real-time?
Can I filter or transform data between Stripe and Brevo?
What Stripe events can trigger a Brevo workflow?
Do I need a paid plan to use Stripe with Brevo?
What if I want Brevo → Stripe instead?
Other apps that pair well with Stripe.
Wire Stripe to Brevo in 2 minutes.
Free tier available. No credit card. No onboarding call.
