Brevo Integrations: A Strong Developer Surface, and a Missing Shopify Listing

Brevo connects to more tools than most email platforms at its price, and publishes a developer surface built for software rather than for marketing. Its navigation describes the catalogue as "150+ digital tools like Shopify, WordPress, Stripe, Zapier and more." ^[2] This page covers what connects, what each plan allows, how the main integrations rate, and one finding that matters for every online store: Brevo's Shopify App Store listing is currently unavailable.

What Brevo connects to

Three kinds of connection.

Native integrations with common tools: Shopify, WordPress, Stripe, Zapier and others, more than 150 in total according to the vendor ^[2].

A developer surface: the vendor describes "Brevo’s developer guides, open API, SDKs, and code recipes" ^[2], plus SMTP relay for transactional email and webhooks for events.

AI assistants: an MCP connection that lets ChatGPT, Claude and other assistants work in the account, described on the pricing page as a way to "Manage campaigns and contacts directly from ChatGPT, Claude & other AI tools" ^[2].

For most small businesses, the native integrations and Zapier cover the need. For developers, the API and SMTP relay are the reason to choose Brevo at all.

## Integrations by plan

From the vendor's plan descriptions ^[5]:

	Free	Starter	Standard	Professional
Native integrations	yes	yes	yes	yes
API and SMTP relay	yes	yes	yes	yes
Outbound webhooks	yes	yes	yes	yes
Inbound webhooks	no	no	no	yes
MCP for ChatGPT and Claude	not listed	yes	yes	yes
Global data feeds	no	yes	yes	yes
Personalised data feeds	no	no	no	yes

The API is available on every plan, which makes the free plan a usable testing ground for developers. The limits that matter on Free are sending, 300 emails a day, and automation, 2,000 contacts ^[6].

Transactional email and SMTP

Transactional email is where Brevo began, under the Sendinblue name, and it is still one of its strongest products. The product page describes sending "real-time email, SMS, & WhatsApp messages triggered via SMTP relay and API" ^[2].

The same email credits cover marketing and transactional sends: "you can use your email credits to send both marketing and transactional emails" ^[7]. A small app can send password resets, receipts and a monthly newsletter from one account and one budget.

On the free plan the two share the 300-a-day limit. Once it is used, "up to 1,000 additional emails are held in a retry queue. Emails beyond this queue are not delivered." ^[6] Keep campaigns off a free account that also carries critical transactional email.

## WordPress

The official plugin, published by Brevo, scores 4.1 from 285 ratings on WordPress.org ^[16]. The distribution is 206 five-star, 14 four-star, 8 three-star, 11 two-star and 45 one-star. Most sites run it without trouble; a minority report serious problems.

That is a strong result in this category. MailerLite's official WordPress plugin, in our measurement, scored 3.0 from 40.

The plugin connects signup forms and can route WordPress emails through Brevo's SMTP. Test it on a staging site, confirm new subscribers land in the right list, and check that transactional emails from WordPress still arrive after activation.

Shopify: the listing is unavailable

Brevo's Shopify App Store listing currently reads: "This app is not currently available on the Shopify App Store. If you have support questions, contact Brevo directly." ^[17]

Search engines still show an old rating of 4.9 for the listing. That rating does not describe anything a store can install from the Shopify App Store today.

Brevo still lists Shopify among its integrations ^[2], and its pricing page describes e-commerce features such as abandoned-cart recovery and product recommendations. A store considering Brevo should ask the vendor which Shopify connection is supported now, test it on a development store, and confirm that orders and customers sync before relying on it.

For comparison, Klaviyo's Shopify app scored 4.7 from more than 3,000 reviews in our Klaviyo measurement.

## Stripe and payments

Stripe is among the integrations Brevo names ^[2]. Brevo also has its own payment features, which the account-closing checklist refers to as payment links to remove from a website before closing an account ^[12].

For a service business, that means a payment link in an email or on a landing page, with the payment recorded in Brevo. For a store, the e-commerce integration matters more than Stripe.

Zapier and the long tail

Zapier is how Brevo reaches tools without a native integration. Typical uses: adding a webinar registrant to a list, creating a CRM deal when a form is submitted, or sending a contact to an accounting tool when they pay.

Zapier is priced separately by tasks. For high-volume syncs, Brevo's API or webhooks are cheaper and more reliable.

Whatever the route, add only contacts who opted in. Brevo tests early campaigns to new contacts on a random subset and suspends accounts when bounces, unsubscribes or complaints cross published thresholds ^[13]. An automation that pours unconsented contacts into a list is the fastest route there.

Webhooks and data feeds

Outbound webhooks, available on every plan ^[5], notify another system when something happens in Brevo: an email opened, a contact unsubscribed, a form submitted. Inbound webhooks, on Professional, let other systems trigger actions in Brevo.

Data feeds pull external content into emails: product lists, prices, articles. Starter includes global data feeds connected to an external source or API; Professional adds personalised feeds and a recently viewed feed ^[5].

For a developer, webhooks and feeds turn Brevo into a messaging layer for an existing system rather than a separate marketing tool.

The pricing catalogue as an integration

One unusual integration is the price list itself. Brevo publishes its pricing as a public API and as a Markdown file "intended as a human and LLM-friendly interpretation of the public pricing catalog" ^[3].

That means a finance team, a procurement tool or an AI assistant can read Brevo's current prices directly, in seventeen currencies, without scraping a page. Every price table in our Brevo coverage comes from it.

No other email vendor we have measured publishes its pricing this way.

Integrations and the free plan

Integrations work on the free plan, with the plan's limits. The daily 300-email limit applies to everything sent, including emails triggered by integrations. Automation accepts up to 2,000 contacts ^[6]. And a free account left without login can be deleted, taking its integrations' data with it ^[10].

For a small site, Brevo Free plus the WordPress plugin is a capable starting point. For anything that sends more than 300 emails on a busy day, budget for Starter.

How the integration picture compares

On breadth, Brevo is near the top of our email set: 150+ native integrations, an open API with SDKs, SMTP relay, webhooks and an MCP connection. On WordPress, its plugin is the best-rated official plugin we have measured among the email platforms. On Shopify, it currently has no available App Store listing, which is a serious gap for e-commerce.

We score Brevo 3.6 out of 5 on integrations. The score reflects a strong developer surface and WordPress plugin, held down by the Shopify gap.

Choosing your setup

A WordPress site: the official plugin, tested on staging, with forms routed to a dedicated list.

A developer or app: API and SMTP relay for transactional email, outbound webhooks for events, and a paid plan once daily volume passes 300.

A Shopify store: confirm the supported integration with Brevo before committing, and compare Klaviyo.

A team using AI assistants: Starter or above for the MCP connection.

Anything else: Zapier for low volume, the API for high volume, with Brevo owning consent and unsubscribes.

A worked example: an app with transactional and marketing email

A small software company sends about 6,000 transactional emails a month, mostly sign-up confirmations and password resets, and a monthly product newsletter to 3,000 users.

Sending. 6,000 transactional plus 3,000 marketing is 9,000 emails a month. Contacts. 3,000 users need the 20,000-email tier, the first that stores more than 2,500 contacts ^[5].

Plan. Starter at 20,000 emails costs $32 a month; Standard $69 ^[3]. The company needs no automation beyond a welcome email and is happy with the Brevo footer on transactional mail, so Starter.

Setup. SMTP relay for the application, the API for adding users to the newsletter list, and an outbound webhook to record unsubscribes in the company's own database.

Result. One account, one bill of $32 a month, for both kinds of email. Separate transactional and marketing providers would usually cost more and need two sets of authentication records.

Testing an integration before you rely on it

Test every integration end to end before your list depends on it.

1. Use a staging site or development store, not production.
2. Create a test contact through the integration, not by hand, and check it lands in the right list.
3. Check that the automation or welcome email it should trigger actually starts.
4. Unsubscribe the test contact and confirm the integration does not add it back on the next sync.
5. For transactional email, send each message type once and check delivery and formatting.
6. Watch the contact count, because an integration that adds contacts can cross a tier's cap ^[8].

Then test near the limits. On the free plan, see what happens on a day when 300 emails have already been sent ^[6].

Integrations when you downgrade or cancel

A paid plan ending changes what integrations can do. On the free plan, everything sent through an integration counts toward 300 emails a day, and automation accepts at most 2,000 contacts ^[6]. Inbound webhooks and personalised data feeds, which are Professional features, stop with the plan.

Before cancelling, list every system that sends through Brevo: website forms, application SMTP, store connections, Zapier flows. Move transactional email first, then marketing, and remove Brevo forms and payment links from your website before closing an account, as the vendor's checklist recommends ^[12].

Authentication records

Whatever integrations you use, the sending domain needs its authentication records in place before volume grows. Set up the records Brevo asks for when you add your domain, and keep them when you add other providers. Poor authentication raises bounces and spam-folder placement, which feed the same figures Brevo watches when deciding whether to suspend an account ^[13].

## Common integration mistakes

Syncing every user as a marketing contact. Customers of an app have not necessarily agreed to a newsletter. Sync only those who opted in, and keep the rest in transactional flows.

Ignoring the contact cap. An integration that adds contacts automatically can push an account past 500, 1,500 or 2,500 contacts and trigger an automatic tier upgrade ^[8].

Letting two systems own unsubscribes. Make Brevo the record of who unsubscribed, and send that back to every connected system through webhooks.

Relying on an old marketplace rating. Check that a listing is still available before trusting its score.