Resources · Zapier integration

Brevo Zapier integrationAutomate Brevo with Zapier.

The Brevo Zapier integration gives you 17 triggers, 16 actions and 0 searches. Ten of those triggers are instant, seven are checked on a timer. Together they cover contacts, companies, deals, campaigns and transactional email or SMS.

See the 33 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Brevo Zapier integration does for you

Brevo is a CRM and messaging suite: contacts, companies, deals, email campaigns and transactional messages live in one account. The Zapier integration lets events in Brevo start work in your other tools, and lets those tools write contacts, deals and messages back into Brevo, without anyone copying data by hand.

Three results come up again and again. A cleaner list: when Marketing Email Hard Bounced fires, a Zap can pull that address out of your lists with Unsubscribe Contact. A CRM that fills itself: a signup in a form tool lands in Brevo through Contact Create or Update. And follow-up that runs on its own: when Deal Stage Updated spots a deal moving forward, Send Transactional Email or Send Transactional SMS goes out to the client.

Now the limits. Zapier cannot create or send an email campaign: none of the 16 actions is built for that. The three lookups (Find Company, Find Deal, Search Contact) are listed as actions, not as search steps, so they are billed like any other action. And the triggers are not all equal: the email and list events are instant, while contacts added, companies and deals are checked on a timer.

Comparing tools? The same app is covered on the Brevo n8n integration and Brevo Make integration pages.

Vocabulary

Zapier vocabulary in one minute

Seven words carry this whole page. Here is what each one means, in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more steps that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap, such as a contact unsubscribing in Brevo. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that creates, updates, sends or deletes something for you.
Task
The unit Zapier bills: one action completed successfully. The figure on your plan counts those and nothing else.
Polling vs instant
A polling trigger is checked on a timer that depends on your plan. An instant trigger is pushed by the app the moment the event happens.
Filter
A step that lets the Zap continue only when the data meets a condition you set, such as one deal stage, and stops it otherwise.
Multi-step Zap
Any Zap that goes beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Cost

What Brevo on Zapier really costs

Brevo is not a premium app: it works from the free Zapier plan, within that plan's limits.

  • Premium appNo
  • Free plan100 tasks a month, two-step Zaps
  • Instant triggers10 of 17

The trigger never costs a task, and Zapier checking Brevo for new data costs nothing either. Each action that succeeds counts as one task, and a failed one is not counted. The free plan gives 100 tasks a month, two-step Zaps only, and checks polling triggers every 15 minutes; the ten instant Brevo triggers ignore that grid. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan.

Connect

Connect your Brevo account

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Brevo account linked once, then reused by every Zap step that talks to Brevo.

  2. 02

    Find Brevo

    Type Brevo in the dialog's search box, select it and click Add connection. A tab opens on the Brevo side. You need an existing Brevo account, with access to the contacts, deals or lists your Zaps will touch.

  3. 03

    Sign in and grant access

    Log in to Brevo in that tab and allow Zapier to use the account. From then on, every Brevo trigger or action can use that connection. You do not set it up again for each Zap.

First Zap

Your first Zap with Brevo

GoalWhen a deal reaches the stage that matters to you, the client receives an email from your Brevo account.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose Brevo as the trigger app, then Deal Stage Updated as the event, and select the Brevo connection you created earlier.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent deal changes of the account. Pick one that sits in the stage you care about.

  3. 03

    Add a filter

    Add a Filter step and set the stage field, the rule and the value, so the Zap only goes on for that one stage. This makes the Zap multi-step.

  4. 04

    Add the email action

    Add Brevo again, choose Send Transactional Email and fill the recipient, sender, reply-to address and subject, mapping data from the deal.

  5. 05

    Test, then publish

    Test the action and check the email that arrives. Then click Publish to switch the Zap on. On the free plan, the filter blocks this step.

Triggers

The 17 Brevo triggers

17 events start a Zap when something happens in Brevo, and 10 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Campaign Status

Polling trigger

In Zapier“Triggers when the status of a Brevo campaign is updated.”

Keeps an eye on your email campaigns and starts the Zap when one of them reaches the status you chose to watch. Handy for telling people outside Brevo that a campaign has moved on.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
the sales team wants a heads-up in its chat tool whenever a campaign changes state, so it can expect replies.
Watch out
the status to watch is a required setting; the trigger follows that one status, not every change.
2

Link Clicked

Instant trigger

In Zapier“Triggers when a Brevo contact clicks on any link in a Brevo email campaign.”

Fires as soon as a contact clicks any link inside one of your Brevo email campaigns. It is the clearest signal of interest the integration offers, because a click means the person did something.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a click on a pricing link should create a follow-up task for a sales rep while the interest is fresh.
Watch out
by default you only get the event and the email address; set the option to return all contact data if later steps need more.
3

Company Added

Polling trigger

In Zapier“Triggers when a company is created in Brevo.”

Starts the Zap each time a new company record appears in the Brevo CRM.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
accounting or a project tool needs a matching customer file every time sales adds a new account in Brevo.
Watch out
companies that existed before the Zap was published are never picked up, so sync the backlog separately.
4

Company Updated

Polling trigger

In Zapier“Triggers when a company is updated in Brevo.”

Reacts when an existing company record is edited in Brevo, so other tools can stay in step with the CRM.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a billing tool must reflect a new address or owner as soon as someone corrects it in Brevo.
Watch out
if the same Zap writes back to that company with Add or Update Company, it sets itself off again and loops.
5

Contact Added

Polling trigger

In Zapier“Triggers when a Brevo contact is added.”

Picks up every new contact created in your Brevo account and hands it to the rest of the Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
each new contact should also land in a shared spreadsheet or in a second CRM used by another team.
Watch out
this one is polled; if speed matters and the contact joins a list, the instant list trigger reacts sooner.
6

Contact Subscribed to Specific List(s)

Instant trigger

In Zapier“Triggers when a Brevo contact is subscribed to specific list(s).”

Watches one or more lists you select and starts the Zap the moment a contact is subscribed to any of them. It is the precise version of a new-contact trigger.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
joining a webinar list should immediately add the person to the registration tool.
Watch out
picking the list is mandatory, and only the email and event come back unless you ask for all contact data.
7

Contact Unsubscribed

Instant trigger

In Zapier“Triggers when a contact unsubscribes from an email campaign in Brevo.”

Signals that a contact has unsubscribed from an email campaign, which is exactly the moment other tools should stop writing to that person.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a second mailing tool or a sales sequence must drop the address as soon as the person opts out.
Watch out
the default output is limited to the event and the email address; turn on the full contact data option for names or attributes.
8

Contact Updated

Instant trigger

In Zapier“Triggers when a Brevo contact is updated (either list(s) they belong to or contact data).”

Goes off whenever a contact changes, either in its data or in the lists it belongs to. It is the broadest contact trigger, and the only instant one about contact data.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a support desk must always show the same phone number and company as Brevo.
Watch out
a Zap that updates the same contact with Contact Create or Update fires this trigger again, so add a filter or write elsewhere.
9

Deal Added

Polling trigger

In Zapier“Triggers when a deal is created in Brevo.”

Notices each new deal opened in the Brevo CRM and passes its details to the next steps.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a manager wants a line in a pipeline spreadsheet or a ping in chat for every opportunity the team opens.
Watch out
deals created in bulk, after an import, can arrive as a large batch that Zapier's flood protection holds back.
10

Deal Stage Updated

Polling trigger

In Zapier“Triggers when a deal's stage is updated in Brevo.”

Tracks movement through your pipeline: the Zap starts when a deal is moved to another stage. Each move to a new stage is one run.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
reaching a signing stage should send the client a welcome email or alert the onboarding team.
Watch out
it fires on every stage change, so a filter on the stage you care about is usually needed, which means a paid plan.
11

Deal Updated

Polling trigger

In Zapier“Triggers when a deal is updated in Brevo.”

Any update to a deal that already exists in Brevo sets this one off, and the deal goes on to the next steps.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a forecast sheet outside Brevo should mirror deal values as sales reps adjust them.
Watch out
when only stage moves matter to you, Deal Stage Updated is the narrower trigger.
12

Marketing Email Delivered

Instant trigger

In Zapier“Triggers when a Brevo campaign marketing email is delivered.”

Confirms that a campaign email actually reached the recipient's mailbox, one run per delivered message.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a log of who received a given campaign must be kept in a spreadsheet for compliance or reporting.
Watch out
a big campaign means one run per recipient; each action that follows costs a task every time, which drains a 100-task plan fast.
13

Marketing Email Hard Bounced

Instant trigger

In Zapier“Triggers when a Brevo campaign marketing email is hard bounced.”

Reports a campaign email that bounced permanently, meaning the address cannot receive mail. Writing to it again is pointless.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the bad address should be flagged in the CRM your sales team uses, so nobody keeps writing to it.
Watch out
you get only the event and the email by default; switch on all contact data to find the matching record elsewhere.
14

Marketing Email Opened

Instant trigger

In Zapier“Triggers when a Brevo campaign marketing email is opened.”

Starts a Zap when a contact opens one of your campaign emails, a softer signal than a click but a far more frequent one.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
engagement scoring kept in another tool should rise for each contact who opens a newsletter.
Watch out
opens add up quickly on a large list, and every action after this trigger counts as a task on each run.
15

Transactional Email Hard Bounced

Instant trigger

In Zapier“Triggers when a Brevo transactional email is hard bounced.”

Covers the other side of Brevo: a one-to-one email, such as an order confirmation or a password reset, that bounced for good.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
support should hear about a customer who will never get their receipts, and ask for a valid address.
Watch out
it only covers transactional mail; campaign bounces come through Marketing Email Hard Bounced, a separate trigger.
16

Transactional Email Delivered

Instant trigger

In Zapier“Triggers when a Brevo transactional email is delivered.”

Tells you that a transactional email, sent by your app or by a Zap, reached the inbox of its recipient.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a customer file in your helpdesk should show that the contract or invoice email really arrived.
Watch out
a Zap that sends transactional email and also listens to this trigger is easy to loop, so keep the two apart.
17

Transactional Email Opened

Instant trigger

In Zapier“Triggers when a Brevo transactional email is opened.”

Fires when someone opens a transactional email, which tells you a quote, invoice or access link has been seen.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a sales rep wants to call right after the client opens the proposal email, not three days later.
Watch out
the output carries only the event and the email by default; enable all contact data to know who it is.
Actions

The 16 Brevo actions

Brevo gives you 16 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

(Deprecated) Add or Update Contact

Action

In Zapier“This action is deprecated, use "Contact Create or Update" instead. Adds or updates a contact.”

The older way to add or update a contact, still listed in the editor with (Deprecated) in front of its name; its own description points to Contact Create or Update.

When to use it
only to understand an existing Zap built with it; new Zaps should use Contact Create or Update.
Watch out
plan to rebuild old steps on the newer action rather than adding fresh Zaps on this one.
2

Add or Update Company

Action

In Zapier“Create a new company or update an existing one in Brevo.”

Creates a company in the Brevo CRM, or updates one with the same name when you allow it.

When to use it
a new customer signed in your billing tool needs its company record in Brevo.
Watch out
names are not case-sensitive, so ACME and acme count as the same company when updating.
3

Delete Company

Action

In Zapier“Deletes the selected company in Brevo using either its name or ID. If a company name is provided and multiple companies share the same name, the most recently created one will be deleted.”

Removes a company from Brevo, found by its name or its ID.

When to use it
a test account or a closed customer must disappear from the CRM when it is removed elsewhere.
Watch out
with a name shared by several companies, the most recently created one is deleted; use the ID to be safe.
4

Find Company

Action

In Zapier“Retrieve the details of a company in Brevo using either its name or ID as input. If a company name is provided and multiple companies share the same name, the most recently created one will be retrieved.”

Fetches the details of a company, by name or ID, so later steps can use its fields.

When to use it
before updating an invoice, you need the company's data as stored in Brevo.
Watch out
this is an action, not a search step, so it costs a task; with duplicate names, the newest company comes back.
5

Contact Create or Update

Action

In Zapier“Creates or updates a contact”

Writes a contact into Brevo, creating it or refreshing an existing one, keyed on the identifier type you choose.

When to use it
every form signup or shop customer should exist in Brevo with up-to-date data.
Watch out
leave the update option off and existing contacts are never overwritten; turn on the email blacklist when there is no consent.
6

Search Contact

Action

In Zapier“Check if a contact exists in Brevo and fetch the contact details. Contact can be found by email, mobile phone number, Brevo contact ID, external ID, Whatsapp ID and landline number.”

Checks whether a contact exists and returns its details, using an email, a phone number, a Brevo ID, an external ID or a WhatsApp ID.

When to use it
a support ticket arrives and you need the customer's Brevo profile before replying.
Watch out
the identifier type is required and must match the value you map in.
7

Add or Update Deal

Action

In Zapier“Create a new deal or update an existing one in Brevo.”

Opens a deal in a pipeline and stage you pick, or updates the deal that already carries that name.

When to use it
a demo request from your website should become an opportunity in the right pipeline straight away.
Watch out
pipeline and stage are both required, so they must exist in Brevo before the Zap can run.
8

Delete Deal

Action

In Zapier“Deletes the selected deal in Brevo using either its name or ID. If a deal name is provided and multiple deals share the same name, the most recently created one will be deleted.”

Deletes a deal from the CRM, identified by name or ID.

When to use it
duplicate or cancelled opportunities should be cleared once another tool marks them as void.
Watch out
if several deals share the name, the newest one goes; mapping the deal ID avoids deleting the wrong one.
9

Find Deal

Action

In Zapier“Retrieve the details of a deal in Brevo using either its name or ID as input. If a deal name is provided and multiple deals share the same name, the most recently created one will be retrieved.”

Retrieves a deal's details from its name or ID, to feed the steps that follow.

When to use it
a signed contract in another app must be matched to its Brevo deal before a status is written anywhere.
Watch out
when several deals share a name, only the most recently created one is returned.
10

Event Create

Action

In Zapier“Create event for selected contact.”

Records a custom event against a contact, such as a purchase or a login, named the way you choose.

When to use it
a payment in another tool should be recorded against the matching Brevo contact.
Watch out
event names accept only letters, numbers, hyphens and underscores; no spaces.
11

Add or Update Associations

Action

In Zapier“Adds or updates associations to companies, deals or contacts in Brevo.”

Links records together: a contact to a company, a deal to a contact, and so on, the way you would in the CRM.

When to use it
after creating a contact and a deal in two earlier steps, this one ties them together.
Watch out
the record type is required: company, deal or contact.
12

Remove Associations

Action

In Zapier“Removes associations between companies, deals, or contacts in Brevo.”

Breaks the link between records, for instance a contact that left a company, while keeping both records.

When to use it
a contact moves to another employer and should no longer appear under the old account.
Watch out
pick the record type carefully, since it decides which links the step looks at.
13

Send Transactional Email

Action

In Zapier“Sends an email from your Brevo account with HTML or plain text content.”

Sends a single email from your Brevo account, in HTML or plain text, to one or several addresses.

When to use it
a quote, a confirmation or an internal alert has to go out the moment something happens in another tool.
Watch out
recipient, sender, reply-to address and subject are all mandatory; map a value you know is always there.
14

Send Transactional SMS

Action

In Zapier“Sends an transactional SMS from your Brevo account.”

Texts a contact from your Brevo account, with the sender name you choose shown on their phone.

When to use it
appointment reminders or delivery notices that people actually read on their phone.
Watch out
past 160 characters the message is split into several SMS, and the sender name is capped at 11 letters and digits or 15 digits.
15

Unsubscribe Contact

Action

In Zapier“Unsubscribe contact from the list(s) he belong to.”

Takes an existing contact off the lists you select, without deleting the contact itself.

When to use it
a customer who cancels in your billing tool should leave the prospect lists at once.
Watch out
the contact must already exist in Brevo, found by email, and at least one list is required.
16

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw request to Brevo using your existing connection, for anything the other actions do not cover.

When to use it
a Brevo feature you need has no ready-made action, and someone on the team can read the Brevo API docs.
Watch out
requests only go to Brevo's own domains, and the stop-on-error choice is mandatory.
When it breaks

When the Brevo Zap breaks

Zapier attaches only a getting-started article to Brevo. Most failures come from how Zaps work and from a few field rules of the app.

The six cases below come from Zapier's general rules and from field rules written into the Brevo operations themselves. Some stop the Zap, others let it run but do the wrong thing. For anything else, see the Zapier troubleshooting page.

  • The Zap keeps triggering itself

    Listening to Contact Updated and writing back with Contact Create or Update makes the Zap set itself off again and again, burning tasks fast.

  • Old contacts and deals are ignored

    A Zap only reacts to what happens after it is published. Contacts, companies or deals already in Brevo are never picked up; moving them is a separate job.

  • A bulk import is held back

    Importing thousands of contacts or deals at once can return a huge batch to a trigger, and Zapier's flood protection may hold it back.

  • The wrong company or deal was deleted

    Delete Company and Delete Deal, given a name shared by several records, remove the most recently created one. Map the ID instead of the name.

  • An SMS arrived in several parts

    Above 160 characters, Send Transactional SMS splits the text into several messages. Keep reminders short, or expect several texts per contact.

  • The SMS test step fails

    With no test mobile number, the test of Send Transactional SMS fails, yet the published Zap still runs. The test itself uses one Brevo SMS credit.
Need help

Need help automating Brevo with Zapier?

A person reads every message.

FAQ

Brevo Zapier integration: common questions

01Is the Brevo Zapier integration free?
Yes, within the limits of the free Zapier plan. Brevo is not a premium app, so it works without a paid subscription. The free plan builds two-step Zaps only, one trigger and one action, with 100 tasks a month. A filter, such as keeping only one deal stage, or a second action turns the Zap into a multi-step one that needs a paid plan. Brevo-side costs, such as SMS credits, are separate from Zapier.
02How many tasks does a Brevo Zap use?
One per action that completes successfully, on every run. The trigger costs nothing, and Zapier checking Brevo for new data costs nothing either. A failed action is not counted. Watch the triggers that fire per recipient, such as Marketing Email Opened or Marketing Email Delivered: one campaign can start the Zap many times, and each run spends tasks on its actions. Find Company, Find Deal and Search Contact are actions too, so they count.
03Is the Brevo Zapier integration real-time?
For ten of the 17 triggers, yes. The email events, link clicks, list subscriptions, unsubscriptions and Contact Updated are instant: Brevo notifies Zapier as soon as they happen, whatever your plan. The other seven, including Contact Added, Company Added, Deal Added and Deal Stage Updated, are polled. Zapier checks them every 15 minutes on the free plan, every 2 minutes on Professional and every minute on Team or Enterprise. A Zap built on an instant trigger shows a lightning bolt in the editor.
04What does it take to connect Brevo to Zapier?
A Brevo account and a Zapier account. From the Apps page in Zapier, add a connection, pick Brevo, sign in through the tab that opens and grant access. Every Brevo step then reuses that connection. Your Brevo user also needs access to the lists, contacts or deals the Zap will read or change, and any pipeline or stage used by Add or Update Deal must already exist. Once that is in place, the steps can be tested on real data.
05Why did Delete Deal remove the wrong deal?
Because it was given a name rather than an ID. When several deals share the same name, Delete Deal removes the most recently created one, and Delete Company behaves the same way with companies. Find Deal and Find Company follow that rule too and return the newest match. The safe habit is to carry the record ID from an earlier step, such as the trigger, and map that ID into the delete action.
06What if the Brevo action you need does not exist?
Look at API Request (Beta) first. It sends a raw request to Brevo through your existing connection, so it can reach features that have no ready-made action, as long as the address belongs to Brevo. It needs someone comfortable with the Brevo API documentation. Creating or sending an email campaign, for instance, has no dedicated action; whether API Request (Beta) can reach it depends on what Brevo exposes, which this page does not cover.
07Zapier, Make or n8n for Brevo?
It depends on your criteria, not on a single winner. On Zapier, Brevo brings 17 triggers, ten of them instant whatever the plan, and 16 actions, with a free plan limited to two-step Zaps and 100 tasks a month. Cost grows with every successful action, so per-recipient events like campaign opens weigh on the plan. List the Brevo events and actions your scenario needs, check that each tool offers them, then estimate what one run costs at your volume before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations