Stripe + Brevo Integration
Illustration · sample data
Sync example
Source
Stripe
Connector status: Live
Destination
Brevo
Connector status: Live
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
customer.email | not_mapped | [email protected] |
marketing_consent | unavailable | unknown |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Stripe + Brevo
Tajo has a Stripe connector. It reads customers, charges, subscriptions and invoices with a Stripe secret key. The Tajo team sets up the key with you. There is no self-serve key field yet.
What You Cannot Do Today
A sync of Stripe customers into Brevo contacts cannot be published. Stripe records no marketing consent on its customers, so no customer can be shown to have agreed to marketing. Tajo refuses any rule that writes contacts or events to Brevo without that proof.
The same holds for payment events. Sending Stripe charges to Brevo as events needs the same consent filter.
What You Can Do
If the same customers buy through a Shopify store, the Shopify sync carries their consent into Brevo. See Shopify + Brevo.
If you need Stripe data in Brevo, tell the team what you want to send.
Doing It Yourself
Stripe publishes an official MCP server: a remote server at https://mcp.stripe.com and a local one, npx -y @stripe/mcp --api-key=YOUR_STRIPE_SECRET_KEY. Stripe’s MCP documentation covers which keys it accepts.
Pair it with Brevo’s MCP server, described in Brevo MCP Server. The consent question does not go away in that setup: you are responsible for sending Brevo only people who agreed to marketing.