Brevo Integrations: Native, Zapier, and API
Brevo’s App Marketplace lists 150+ native apps and plugins — Shopify, WordPress, Stripe, Salesforce and the rest of the usual SMB stack — while the official Zapier connector reaches 9,000+ further apps with roughly 12 triggers and 12 actions. Anything neither surface covers is reachable through REST API v3 at api.brevo.com/v3/ — contacts, transactional email, campaigns, CRM deals, senders, domains, webhooks and inbound parsing — behind 7 official SDKs.
The shape of this differs from a pure relay. Where Postmark and MailerSend expect sending to be wired into your own application, and SendGrid and Mailjet sit in between, Brevo ships plugins a marketer installs without a developer, then leaves the same account addressable over SMTP at smtp-relay.brevo.com. Most deployments use both paths at once, and the credentials are not shared — see SMTP settings for the relay side.
At a glance
Read those as three tiers of effort, not three alternatives. A native connector authenticates in minutes but only does what its author built; Zapier buys breadth at the cost of per-task pricing and polling latency; the API does everything and is yours to maintain. Brevo’s marketplace is the canonical index, but its grid renders client-side and is invisible to crawlers, so the list below is a verified subset.
Integrations directory
The 26 connectors below are the ones that matter for an email-infrastructure decision: surfaces that create contacts, fire automation events, or send mail on your behalf. Each links to its official Brevo listing, tagged NATIVE for a first-party or marketplace app and ZAPIER for one reached through the Zapier connector.
CMS and website builders (4)
The WordPress plugin is the one to know: contact sync, signup forms, chat and SMTP-based sending in one install, with 100,000+ active installs.
Official Brevo plugin adding contact sync, signup forms, chat and SMTP-based transactional sending to any WordPress site.
Connects Drupal sites to Brevo for subscriber management and transactional email delivery.
Captures Squarespace site signups into Brevo lists and enables campaign sending to them.
Routes Webflow form submissions into Brevo contacts and triggers automation workflows.
E-commerce (5)
Brevo builds and maintains the WooCommerce, Magento 2 and PrestaShop connectors itself, a legacy of the Sendinblue era when self-hosted European commerce was its core market.
Syncs WooCommerce customers, orders and product data into Brevo to power abandoned-cart and post-purchase automations.
Real-time sync of customer data, purchase history and order status between Shopify and Brevo, delivered via PushOwl.
Connects a BigCommerce storefront to Brevo for customer sync and lifecycle marketing.
Brevo-built Magento 2 extension for contact sync, transactional email and automation from an Adobe Commerce store.
Long-standing Brevo module pushing PrestaShop order and customer data into Brevo lists and automations.
Forms and lead capture (4)
Sends Elementor form submissions directly into Brevo contact lists without custom code.
Pipes Contact Form 7 submissions into Brevo, a common pairing on sites already sending through the Brevo relay.
Maps Gravity Forms fields to Brevo contact attributes and adds submitters to lists automatically.
Adds WPForms entries to Brevo lists and triggers welcome or nurture automations.
CRM and sales (4)
Brevo ships its own CRM, so these exist to keep an incumbent system of record authoritative while Brevo sends. Budget custom syncs around the contacts limit of 10 requests/second on the General tier — roughly 100x tighter than sending, and the ceiling you hit first.
Bidirectional real-time data sync between Salesforce and Brevo to align sales records with marketing automation.
Syncs HubSpot contacts and lifecycle data with Brevo so campaigns can run off HubSpot CRM records.
Keeps Pipedrive contacts and deal stages in sync with Brevo contacts and sales automations.
Connects Dynamics CRM records to Brevo for enterprise marketing automation.
Payments, data and analytics (4)
Syncs Stripe payment and customer events into Brevo for receipts, dunning and revenue-based segmentation.
Streams Segment customer events and identities into Brevo as a destination for unified profiles.
Adds campaign tracking so Brevo email traffic and conversions are attributed inside Google Analytics.
Connects Airtable bases to Brevo so records can drive contact creation and campaign workflows.
Automation and iPaaS (3)
All three call the same API v3 surface, so the choice is hosting and pricing, not capability. n8n is what EU-hosted teams pick to keep automation in the same jurisdiction as the sending.
Official Brevo connector linking Brevo to 9,000+ apps with 12+ triggers and 12+ actions including Send Transactional Email and SMS.
Visual scenario builder connecting Brevo to hundreds of apps for multi-step marketing automations.
Self-hostable workflow automation node for Brevo, popular with teams wanting EU-hosted automation alongside EU-hosted email.
Messaging and collaboration (2)
Pushes Brevo campaign, contact and deal notifications into Slack channels.
Bridges Intercom conversations and user data with Brevo contacts and messaging.
Frequently asked questions
How do I connect Brevo to WordPress for SMTP and contact sync?
Install the official Brevo plugin (slug mailin) and connect it with a v3 API key from Account SMTP & API. That covers contact sync, forms and chat. Routing WordPress transactional mail is a separate switch: the plugin can take over wp_mail(), or point any SMTP plugin at smtp-relay.brevo.com on port 587 with STARTTLS. The relay will not accept the API key — it wants your SMTP login and SMTP key. Details on SMTP settings.
Does Brevo integrate with Shopify and WooCommerce natively?
Yes, both. The WooCommerce plugin is Brevo-maintained and syncs customers, orders and product data for abandoned-cart and post-purchase flows. The Shopify app is official but delivered through PushOwl, with a separate Shopify Markets listing for cross-border stores. Magento 2, PrestaShop and BigCommerce are native too — a wider self-hosted commerce footprint than most ESPs at this price.
Which CRMs does Brevo integrate with?
Salesforce, HubSpot, Pipedrive and Microsoft Dynamics all have native connectors, with Salesforce documented as bidirectional real-time sync. Brevo also ships its own CRM — free accounts get 50 open deals and 1 pipeline — so the real question is whether to keep an incumbent authoritative or consolidate. Build a custom sync instead and the binding constraint is the contacts rate limit of 10 requests/second, not the sending limit.
How many apps does Brevo connect to through Zapier?
Zapier’s Brevo app page states the connector reaches 9,000+ other apps. Brevo exposes roughly 12 triggers (contact added, updated or unsubscribed; company and deal changes; email delivered, opened or hard bounced; link clicked; campaign status) and roughly 12 actions, including Create or Update Contact, Send Transactional Email, Send Transactional SMS and Create Event, plus a beta raw API Request action.
Can I use Brevo with Make or n8n instead of Zapier?
Yes. Both are listed on Brevo’s marketplace and both call the same API v3 endpoints, so no capability is lost. Make suits branchy scenarios where Zapier’s per-task pricing stops making sense; n8n is self-hostable, which matters if you moved to Brevo for EU data residency. For high-volume sending, calling POST /v3/smtp/email directly beats all three — iPaaS adds per-operation cost and polling latency a 1,000 requests/second endpoint does not need.
Does Brevo have a native Stripe integration for payment-triggered emails?
Yes. The Stripe connector syncs payment and customer events into Brevo, enough for receipts, dunning and revenue-based segmentation without writing webhook glue. For finer control, such as attaching an invoice PDF, use a Stripe webhook that calls POST /v3/smtp/email. Two limits apply there: 99 recipients per transactional message, and 20MB total per email including attachments, dropping to 4MB per attachment when the file sits inside an email template.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
