Resources · Make integration

Brevo Make integrationAutomate Brevo with Make.

A Brevo Make integration turns your email tool into something that keeps working after you close the tab. Make gives Brevo 33 modules, the bricks you drop into an automation: 5 triggers, 22 actions, 6 searches. This page explains what each one is for, then walks you through your first build.

Try the Brevo integration on MakeSee the 33 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can a Brevo Make integration actually automate?

It means your Brevo account, formerly Sendinblue, gets things done without anyone clicking. Make is a visual builder where you chain modules together into a scenario, the automation you assemble on a canvas and leave running. Brevo brings 33 of those modules, so a contact, a list, a folder or a campaign can be created, read, updated or removed by a scenario that works while you are somewhere else.

Welcome messages that start themselves. Watch Contacts notices a new person in your account, Send an Email delivers the first message, and Add Existing Contacts to a List files them where your team expects to find them. Nobody has to remember to do it on a busy day.

A base that stays clean. List Contacts in a List reads who is in a segment, Update a Contact carries over what changed in another tool, and Delete a Contact honours the people who asked to leave.

Numbers that reach the person who asked for them. List Email Campaigns pulls what went out, Get an Email Campaign opens the one under discussion, and Send a Campaign Report mails the PDF report to whoever wanted it.

What Make will not do: it does not design the email, and it does not invent your segmentation. The Brevo documentation also points to the Brevo API reference for anything the listed modules skip, which is a polite way of saying the catalog has edges. The same app exists on the other side of the fence, so the Brevo n8n integration covers the same ground with a different editor, and n8n vs Make lays out the criteria that actually matter. If you would rather learn the editor properly before wiring a live account to anything, the Make training takes the same route at a slower pace.

Connect

How do you connect Brevo to Make?

  1. 01

    Generate an API key in Brevo

    Log in to Brevo, open your Profile Icon and pick SMTP&API. Go to the API Keys tab and click Generate a new API key. Give it a name that says where it will be used, then click Generate.

  2. 02

    Copy the key before it disappears

    Brevo puts the key on screen once. Copy it, park it somewhere safe such as a password manager, then click OK. Come back later and you will see the name of the key and nothing else, so a key you lost is a key you replace rather than recover.

  3. 03

    Paste it into a Make connection

    In Make, add any Brevo module to a scenario and click Create a connection, the step that links your account to Make once for every Brevo module that follows. Name it in the Connection name field, paste the key into API Key, then click Save.

First scenario

Your first scenario: a welcome email for every new contact

GoalWhen a new contact lands in Brevo, Make sends a welcome email and files the person in the right list.

  1. 01

    Create the scenario

    From the Scenarios page, start a new scenario and click the + to place your first module. Type Brevo into the search box and the whole catalog of 33 modules comes up, grouped by what they touch.

  2. 02

    Drop in Watch Contacts

    Pick Watch Contacts as the first module, then click Create a connection if your account is not linked yet. Once the connection exists, the module can read your account and fill its own fields.

  3. 03

    Add the email

    Click the + to the right of the trigger and add Send an Email. Map the details from the first module into the second, so each bundle, meaning one contact travelling through the chain, carries its own address.

  4. 04

    File the contact

    Add Add Existing Contacts to a List behind the email so the person ends up in the right place. Three modules is plenty for a first build, and the + is still there when you want a fourth.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time. Each module then shows the bundles it received, which is where a mapping pointing at the wrong thing gives itself away before anyone gets a strange email.

  6. 06

    Set the clock and switch it on

    Click the clock on the first module to open Scheduling. A new scenario checks every 15 minutes, which is also as fast as the Free plan goes. Flip the scenario on and it runs without you.

Triggers

What starts a Brevo scenario

5 modules start a scenario when something happens in Brevo. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Brevo as soon as it happens.

Brevo1Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a new contact is created.”

Watch Contacts keeps an eye on your contact base and hands each newly created person to the rest of the scenario. One new contact, one bundle, and everything you chained behind it goes to work on that record.

How it fires
scheduled, so Make checks Brevo on the scenario's schedule rather than the second the contact appears.
When to use it
a form on your site drops people into Brevo and you want them greeted, tagged or copied into another tool while the visit is still fresh.
Watch out
each contact handled spends an operation, the unit Make counts on your plan, so a popular signup form and a tight schedule get through a Free plan quicker than you would guess.
Brevo2Watch Lists

Watch Lists

Scheduled trigger

In Make“Triggers when a new list is created.”

A list created in Brevo becomes the starting gun for a scenario. Watch Lists reports it as soon as the next check comes round, with the details Brevo holds on it ready for the modules behind.

How it fires
scheduled, Make asks Brevo for new lists at the rhythm you set on the first module.
When to use it
a colleague creates one list per campaign, and you want a matching folder and a note to the team to appear at the same moment.
Watch out
it reacts to lists being born, not to contacts moving between them. Tracking that movement is a job for a search module run on a schedule instead.
Brevo3Watch Folders

Watch Folders

Scheduled trigger

In Make“Triggers when a new folder is created.”

Folders are the drawers your lists sit in, and this trigger tells a scenario when a new drawer opens. Each folder arrives on its own, carrying what Brevo knows about it.

How it fires
scheduled, Make looks at the folders whenever the scenario is due to run.
When to use it
a folder per client or per quarter is how an account stays readable, and the housekeeping around it should follow by itself.
Watch out
folders get created rarely, so a scenario built on this alone sits idle most of the time while still checking. Give it a calmer schedule than you would give a contact trigger.
Brevo4Watch Email Campaigns

Watch Email Campaigns

Scheduled trigger

In Make“Triggers when a new email campaign is created.”

Every email campaign created in your account shows up here, so the rest of the scenario hears about a send while it is still being prepared rather than long after.

How it fires
scheduled, Make asks Brevo for new campaigns on the scenario's own clock.
When to use it
an approval habit. A campaign gets drafted, and the scenario puts it in front of the people who are supposed to read it before it goes out.
Watch out
creation is not sending, and it is not results either. If what you need is the performance afterwards, Send a Campaign Report is the module that mails the numbers.
Brevo5New Event

New Event

Instant trigger

In Make“Triggers when a new email event occurs.”

New Event is the one Brevo trigger that does not wait its turn. An email event happens in your account, and the scenario is already running on it.

How it fires
instant, Brevo calls Make through a webhook, the address Make hands out so an app can push news to it the moment something occurs.
When to use it
reactions that lose their value after a few minutes, such as passing a warm lead to sales while the person still has the email open.
Watch out
instant only counts while the scenario is switched on, so leave it running rather than starting it by hand when you remember.
Modules

What Brevo can do inside a scenario

Brevo gives you 28 modules in 5 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Contacts

8 modules
Brevo1

List Contacts

Search

In Make“Lists all contacts.”

Pulls the contacts held in your account and passes them along one at a time, so the modules behind it work record by record instead of on a lump of data.

When to use it
a sweep that copies your base somewhere else, or a check that counts who you really have rather than who you think you have.
Watch out
a search returns zero, one or many bundles, and each one spends an operation, so narrow the job before running it on a large base.
Brevo2

List Lists in a Folder

Search

In Make“Lists lists in a folder.”

Reads one folder and returns the lists filed inside it, which is how a scenario learns what a drawer contains before touching anything in it.

When to use it
a client folder where lists pile up over time and your automation needs the current contents, not the ones you remember from last quarter.
Watch out
it stops at the folder you point it at. For the whole account, List Lists is the wider net.
Brevo3

List Contacts in a List

Search

In Make“Lists all contacts in a list.”

Hands you everyone sitting in a given list, one contact per bundle, ready for an email, an update or a copy into another tool.

When to use it
a segment your team works through, where each person gets the same treatment without anybody opening Brevo.
Watch out
a long list means a long run, and a Free plan scenario stops after 5 minutes. Slice the work rather than sweep the whole base in one go.
Brevo4

Get a Contact

Action

In Make“Return details about a contact.”

Fetches one contact and what Brevo knows about it, so the rest of the scenario decides on a real record instead of a guess.

When to use it
another app gives you an address, and you want the Brevo side of the story before writing anything back.
Watch out
it reads, it never writes. Anything that has to change afterwards goes through Update a Contact.
Brevo5

Add Existing Contacts to a List

Action

In Make“Adds existing contacts to a list.”

Puts contacts that already exist into a list. The records stay exactly as they were, only their membership changes.

When to use it
a customer becomes eligible for a campaign and has to join the list that feeds it, today rather than at the next manual import.
Watch out
it assumes the person is already in your base. When they might be new, Create a Contact belongs earlier in the chain.
Brevo6

Create a Contact

Action

In Make“Creates a contact.”

Writes a new person into Brevo from whatever the scenario collected upstream, so the record exists at the moment it is needed.

When to use it
a form, a booking or a purchase happening outside Brevo, where the contact has to land in your base before any message can go out.
Watch out
run it on somebody already there and you are duplicating rather than enriching. A Get a Contact ahead of it tells you which case you are in.
Brevo7

Update a Contact

Action

In Make“Updates a contact.”

Changes what Brevo holds on a person who is already in the base, and leaves the rest of the record alone.

When to use it
your other tool is where a phone number or a status really changes, and Brevo should not be the last to hear about it.
Watch out
updates overwrite. Send an empty value into a field and the old one is gone, so map only what you actually mean to change.
Brevo8

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a contact from the account for good. Nothing inside Make brings that record back.

When to use it
an erasure request that has to be honoured in the tool itself, not just noted in a ticket somewhere.
Watch out
a delete has no undo. Test the branch with Run once on a record you created for the occasion before letting it near real people.

Lists

5 modules
Brevo9

List Lists

Search

In Make“Lists all lists.”

Returns every list in the account, one per bundle, which gives a scenario the lay of the land before it picks a target.

When to use it
an audit of what exists, or a step that has to find a list by name because a name is all your form sends over.
Watch out
how many come back depends on the account that day. Build the steps behind it so they cope with none as calmly as with many.
Brevo10

Get a List

Action

In Make“Returns details about a list.”

Opens one list and reports its details, so a later step knows what it is dealing with before it acts.

When to use it
a scenario that has to confirm a list is still there before adding anyone to it.
Watch out
details are not contents. To see who is inside, List Contacts in a List is the module that reads the membership.
Brevo11

Create a List

Action

In Make“Creates a list.”

Makes a new list in the folder you choose, so a scenario can build structure instead of asking somebody to click through the interface.

When to use it
one list per event, per client or per campaign, created at the same moment the thing itself comes into being elsewhere.
Watch out
nothing stops two runs from producing two lists with the same name. A List Lists check first keeps the account readable.
Brevo12

Update a List

Action

In Make“Updates a list.”

Renames a list or moves it, without disturbing the contacts inside.

When to use it
a naming convention that changed, or a list that belongs in a different folder now the client has moved on to another project.
Watch out
the people stay where they are. Moving a list is not moving contacts between lists, which is what Add Existing Contacts to a List is for.
Brevo13

Delete a List

Action

In Make“Deletes a list.”

Takes a list out of the account. The contacts themselves survive, the grouping does not.

When to use it
housekeeping once a campaign is over and a temporary list has done its job, so nobody sends to it by accident months later.
Watch out
like every delete, it is final. Put a filter on the name, or a human approval, in front of it before it runs on a schedule.

Folders

5 modules
Brevo14

List Folders

Search

In Make“Lists all folders.”

Reads the folders in the account and passes each one along, which is how a scenario discovers the structure it is meant to work within.

When to use it
a tidy-up pass, or a step that has to locate the right folder by name before it files anything.
Watch out
folders barely change, so running this on every execution spends operations on an answer that was the same last time.
Brevo15

Get a Folder

Action

In Make“Returns details about a folder.”

Returns what Brevo knows about a single folder, so the scenario can look before it writes.

When to use it
a branch that should only carry on if the folder a client is supposed to have really does exist.
Watch out
this reads one folder. To see the lists filed inside it, List Lists in a Folder is the right module.
Brevo16

Create a Folder

Action

In Make“Creates a folder.”

Adds a folder, giving your lists somewhere to live before anything tries to file itself.

When to use it
onboarding a client or opening a new quarter, where the structure should appear without anyone remembering to make it first.
Watch out
the folder has to exist before the lists that go in it. A scenario that does those two in the wrong order fails on the second module.
Brevo17

Update a Folder

Action

In Make“Updates a folder.”

Changes a folder's name, leaving the lists inside untouched.

When to use it
a client rebrand, or a folder named in a hurry that now has to match the convention everyone else follows.
Watch out
anything that looks the folder up by name will be looking for the old one after this runs, so update both sides in the same scenario.
Brevo18

Delete a Folder

Action

In Make“Deletes a folder.”

Removes a folder from the account.

When to use it
the end of a client relationship, once the lists inside have been dealt with on purpose rather than by accident.
Watch out
look inside first with List Lists in a Folder. Deleting a container nobody opened is how a scenario throws away work that was still in use.

Campaigns

5 modules
Brevo19

List Email Campaigns

Search

In Make“List all email campaigns.”

Returns the email campaigns in the account, one per bundle, so a scenario can work through them instead of somebody scrolling.

When to use it
a recap you assemble from what actually went out, or a step that finds the campaign matching a name typed in another tool.
Watch out
it is a search, and searches are open-ended. Filter early, because the modules behind it will run once per campaign that comes back.
Brevo20

Create an Email Campaign

Action

In Make“Creates a new campaign.”

Sets up a new email campaign in Brevo from data the scenario already has in hand.

When to use it
a launch, a seasonal offer or a client deliverable, where the campaign should exist the moment the brief is approved rather than the evening before.
Watch out
creating is not sending. What comes out of this module is a campaign that still needs a human to look at it properly.
Brevo21

Get an Email Campaign

Action

In Make“Returns details about an email campaign.”

Opens one campaign and returns its details, so the scenario reads the real thing rather than assuming.

When to use it
a check before an update, or a step that reports on the specific send somebody asked about this morning.
Watch out
point it at the campaign you mean. Fed by List Email Campaigns without a filter, it opens all of them, one operation at a time.
Brevo22

Update an Email Campaign

Action

In Make“Updates an email campaign.”

Modifies a campaign that already exists, so a correction made elsewhere reaches the send itself.

When to use it
a date that moved or a subject line approved late, where retyping by hand is exactly how mistakes get in.
Watch out
map only the parts you want changed. A field you send empty is a field you emptied.
Brevo23

Delete an Email Campaign

Action

In Make“Deletes an email campaign.”

Removes a campaign from the account, permanently.

When to use it
clearing the drafts a test scenario left behind, so they stop cluttering the list your team scrolls through.
Watch out
there is no recovery step in Make. Try the branch with Run once on something disposable before it goes anywhere near a real campaign.

Other

5 modules
Brevo24

Send an SMS

Action

In Make“Sends a transactional SMS.”

Sends one transactional text message from your account, the kind that carries a code, a confirmation or an alert rather than a campaign.

When to use it
a booking confirmed, an order ready to collect, anything where an email would simply be read too late.
Watch out
one message is one operation, and a scenario looping over a list sends as many as it finds. Filter first, count second.
Brevo25

Send an Email

Action

In Make“Sends a transactional email.”

Fires a single transactional email, the one-to-one kind that answers something a person just did.

When to use it
a welcome, a receipt, or an internal heads-up when the scenario finds something that deserves a human look.
Watch out
transactional is not a campaign. For a send to a whole list, with everything a campaign carries around it, the campaign modules are the right family.
Brevo26

Send a Campaign Report

Action

In Make“Sends a PDF campaign report to the specific email.”

Mails a PDF report on a campaign to an address you choose, so the numbers arrive without anybody logging in to fetch them.

When to use it
a client who wants results after each send, or a manager who will never open Brevo but always opens an attachment.
Watch out
the report goes where you point it. Build the address from the scenario data rather than typing it once and forgetting whose it was.
Brevo27

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Brevo API through the connection you already set up, which covers what the listed modules leave out.

When to use it
a Brevo capability with no module of its own, found in the Brevo API reference that the app documentation points you to.
Watch out
this is where Make stops holding your hand. You pick the endpoint and what gets sent, so read the reference before wiring it into anything that writes.
Brevo28

Get My Account

Action

In Make“Return details about my account.”

Returns the details Brevo holds on your own account, which is the fastest way to prove a connection works at all.

When to use it
the first module you drop in when a scenario refuses to authenticate and you want to know whether the key or the mapping is at fault.
Watch out
it still spends an operation every time it runs, so use it while building and take it back out before you switch the scenario on.
Need help

Need help automating Brevo with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Brevo Make integration free?
Yes on the Free plan, with limits you will notice. Brevo is a standard app, and standard apps come with every Make plan alongside the 3000+ others in the catalog. The Free plan allows 2 active scenarios, a floor of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans bring the floor down to 1 minute, lift the limit on active scenarios and stretch execution to 40 minutes. What your Brevo account itself costs is a separate question and depends on the plan you hold there.
02What do you need to connect Brevo to Make?
A Brevo account and an API key from it. The documentation lists no other prerequisite: no paid tier, no extra app, no approval step. You generate the key from your profile menu under SMTP&API, on the API Keys tab, and Brevo shows it to you exactly once. In Make, that key goes into the API Key field of a new connection, which is the link between your account and every Brevo module you add afterwards. One connection covers the whole account, so this is a one-time job you do at the start and never repeat.
03Does a Brevo trigger react in real time?
One of the five does, the other four do not. New Event is instant: Brevo calls Make through a webhook the moment an email event happens, and the scenario starts on that call. Watch Contacts, Watch Lists, Watch Folders and Watch Email Campaigns are scheduled, meaning Make goes and asks Brevo whether anything is new, at the rhythm set on the first module. A new scenario checks every 15 minutes, and 15 minutes is also as fast as the Free plan is allowed to go. Paid plans take that down to 1 minute, which is close enough for most work.
04What if a Brevo module is missing or a limit gets in the way?
Reach for Make an API Call. Brevo has it, and it calls any endpoint of the Brevo API using the connection you already made, which is the answer whenever the 33 modules do not go far enough. The Brevo documentation inside Make points at the Brevo API reference for exactly that situation. If the limit belongs to Make rather than to Brevo, look at the shape of the scenario before blaming the app: a search returning far more than you expected, a run that outgrows the 5 minutes of the Free plan, or a schedule tighter than your plan permits.
05Make or n8n for Brevo?
It depends on who will maintain it. Make suits the case where the person building the scenario is not a developer: the canvas, the module names and Run once put a working automation within reach without writing a line of code. n8n suits a team that wants to self-host, drop a bit of code into the middle of a workflow and keep everything in version control. Both cover Brevo properly. The honest test is whether your automations will live with the marketing side or the technical side, because that is what decides who opens the editor again down the line.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations