Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Marketing ]

Brevo integration for your workflows.

Connect Brevo to Collabase once and use 7 actions and 8 triggers in your workflows. No code needed, hosted in Switzerland.

Sign-inAn API key
CategoryMarketing
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

Brevo in Collabase

Connect Brevo to Collabase once and use 7 actions and 8 triggers in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

Email, SMS and contact marketing platform, formerly Sendinblue.

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Brevo and connect your account.
  3. Add a trigger or an action to the workflow.
  • Log in to Brevo.
  • Open the account menu, go to SMTP & API and open the API Keys tab.
  • Click Generate a new API key, name it and copy the key.

[ Marketing ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Brevo

What can I automate with Brevo in Collabase?

Brevo brings 7 actions and 8 triggers, for example Create or Update Contact, Find Contact, Unsubscribe Contact, Send Transactional Email and 3 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Brevo to Collabase?

You open the integrations in the workspace settings, choose Brevo and connect your account once, using an API key. After that all triggers and actions are available in the workflow.

Can Brevo start a workflow?

Yes. Brevo provides 8 triggers, for example Contact Added to List, Contact Updated, Contact Deleted and 5 more. The workflow runs as soon as the event happens.

Does the Brevo integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.