Start a workflow from a Brevo email event or new contact

Two Brevo triggers start a run the moment Brevo reports something:

• Brevo · Email event — When a transactional email Brevo sent is delivered, opened, clicked or bounces.
• Brevo · New contact — When a contact is added to a Brevo list.

Both are instant triggers. Publishing makes the webhook in Brevo for you, and nothing needs pasting — see How instant triggers work.

Who can do this

Workspace Admins and Editors, on every plan — Brevo is not a premium connection. Viewers see the trigger and its status but cannot change it.

Before you start

A Brevo connection — see Connect Brevo.

Steps

Set up Email event:

1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.

2. Under Brevo, select Email event — it reads Brevo · instant. Or type Brevo in Search triggers.

3. In Connection, choose your Brevo connection — for example Consulace Brevo.

4. In Event, choose what starts a run: Every event (the default), Delivered, Opened, Clicked, Hard bounce, Soft bounce, Marked spam or Unsubscribed.

5. The panel reads Publishing sets this up in Brevo; unpublishing takes it away. It starts with what happens after that.

6. Add the steps, then Publish. Bizomate makes a webhook in Brevo named Bizomate · Email event, for the event you chose — or for all seven with Every event.

   The panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Set up New contact:

1. In the trigger picker, under Brevo, select New contact.
2. In Connection, choose your Brevo connection.
3. Optionally, in Only this list, choose a list — Empty takes every list.
4. Add the steps, then Publish. Bizomate makes a webhook in Brevo named Bizomate · New contact.

Test with a real event:

1. Send a transactional email — with Brevo · Send a transactional email and Run this step, say — or add a contact to the list in Brevo.
2. Within seconds the panel reads Listening — instant — Last event 10:45 · delivered · rohan@consulace.com, or New contact · asha@consulace.com.
3. On Output, select Use the last event, then Test run.

What the trigger gives

Email event — each event is one item:

New contact — each contact added is one item:

Use them in later steps as {{ trigger.email }} and so on. Look up the contact's other details with a Brevo step.

What happens next

• Each event, or each contact added, starts one run of the live version, in Production, named after it.
• Changing the event, the list or the connection and publishing deletes Bizomate's old webhook in Brevo and makes a new one.
• Changing to another trigger and publishing, or deleting the workflow, deletes the webhook in Brevo.

Good to know

• Email event covers transactional email only — what Brevo sends through its API or SMTP, as Send a transactional email does. Campaigns sent from Brevo do not report here.
• Each workflow has its own webhook in Brevo. You can see them on Brevo's webhooks page, named Bizomate · Email event and Bizomate · New contact. Leave them be: deleted in Brevo, the trigger hears nothing, and Bizomate does not notice.
• New contact hears every way a contact joins a list — a form, an import, someone in Brevo, or a Bizomate step such as Add contact to list. A workflow that adds contacts to the same list it listens to starts itself again.
• Opens are estimates. Brevo counts an open when the email's images load.
• Brevo does not sign its calls. The 48-character code in the address is the secret.

If something goes wrong

Related

• How instant triggers work
• Connect Brevo
• Send an email with Brevo
• Add or update a Brevo contact, or change its lists