Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
HeyReach
Brevo

Connect HeyReach and Brevo

Explore ready-made HeyReach and Brevo templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate HeyReach with Brevo and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

HeyReach
Trigger: Watch Campaign Completed
Brevo
Action: Select an action
1. Select a trigger

  • This event notifies you when a HeyReach campaign has been completed.

  • This event is triggered when a LinkedIn account accepts your connection request as part of a HeyReach campaign.

  • This event notifies you when a connection request has been sent to a LinkedIn account through a HeyReach campaign.

  • This event occurs when you start following a LinkedIn profile through a HeyReach campaign.

  • This event notifies you when you receive the first reply to a LinkedIn InMail message that is part of a HeyReach campaign.

  • This event is triggered when you send a LinkedIn InMail message through a HeyReach campaign.

  • This event occurs when you add or remove tags from a contact in HeyReach.

  • This webhook event is sent when a you have liked a LinkedIn Profile’s post as part of a HeyReach campaign.

  • This webhook is activated when you receive the first reply to a LinkedIn message as part of a HeyReach campaign.

  • This event occurs when you send a LinkedIn message through a HeyReach campaign. Connection request messages are not tracked by this event.

  • This event is sent when you view a LinkedIn profile as part of a HeyReach campaign.

2. Select an action

  • Adds existing contacts to a list.

  • Creates a contact.

  • Creates a folder.

  • Creates a list.

  • Creates a new campaign.

  • Deletes a contact.

  • Deletes a folder.

  • Deletes a list.

  • Deletes an email campaign.

  • Return details about a contact.

  • Returns details about a folder.

  • Returns details about a list.

  • Returns details about an email campaign.

  • Return details about my account.

  • Performs an arbitrary authorized API call.

  • Sends a PDF campaign report to the specific email.

  • Sends a transactional email.

  • Sends a transactional SMS.

  • Sends a transactional SMS.

  • Updates a contact.

  • Updates a folder.

  • Updates a list.

  • Updates an email campaign.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between HeyReach and Brevo.

Add Existing Contacts to a List
Adds existing contacts to a list.
Action
Add Lead To Campaign
Adding a lead in a HeyReach campaign
Action
Add Lead To List
Adds a lead to a lead list
Action
Create a Contact
Creates a contact.
Action
Create a Folder
Creates a folder.
Action
Create a List
Creates a list.
Action
Create an Email Campaign
Creates a new campaign.
Action
Create Empty List
Create an empty lead or company list.
Action
Delete a Contact
Deletes a contact.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.