Marketing integration guide
Brevo + UbiGrowth workflows
Brevo is an email and SMS marketing platform (formerly Sendinblue) that owns contacts, campaigns, and transactional sends. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Brevo part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a marketing workflow around Brevo with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Contact, List, Campaign, Transactional Email, SMS, and Automation. Brevo carries marketing and transactional sending on one contact record, so unsubscribing from marketing must not stop transactional delivery. The two consent states are separate and easy to conflate.
Brevo is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Marketing integrations usually fail at the join, not at the connection. Brevo can report on what it did, but connecting that to what happened downstream requires a shared definition of a lead, an opportunity, and a sourced deal that most organizations have never actually written down.
Without those definitions, every reporting cycle turns into a negotiation. Marketing counts one number, sales counts another, and the meeting is spent reconciling definitions instead of deciding what to do next.
You're likely here because
- Campaign reporting is reconciled by hand every cycle
- Marketing and sales count leads and opportunities differently
- Conversion context is lost before anyone follows up
Record model
What a Brevo integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Brevo's.
Identity and matching
Brevo carries marketing and transactional sending on one contact record, so unsubscribing from marketing must not stop transactional delivery. The two consent states are separate and easy to conflate.
Start here
Read transactional send outcomes for one lifecycle moment and stage a human follow-up where delivery succeeded but the intended action did not happen.
What this will not do
It will not make list quality irrelevant. Brevo's cost model rewards sending more; the integration should be reducing sends that have no reason behind them.
The constraint to plan around
Sending limits and dedicated-IP warmup rules apply per plan, so a workflow that increases volume can degrade deliverability before it increases response.
Build notes
What you actually have to reason about in Brevo.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| emailBlacklisted / smsBlacklisted | per-channel suppression, so blocking one does not block the other |
| listIds[] | membership, which drives campaign targeting |
| attributes | account-defined contact fields, typed on creation |
| messageId | the handle for a transactional send, needed to correlate delivery events |
| modifiedAt | the incremental cursor, shared across marketing and transactional contact changes |
Authentication
API key, account-wide and unscoped. Marketing and transactional sending share the same credential, which means a key leaked from a transactional service can send campaigns.
Events and delivery
Webhooks cover both marketing and transactional events, configured separately per type. Transactional delivery events are the operationally useful ones, because they reveal failures the application never sees.
Workflow
How the Brevo workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Agree the definitions
Lead, qualified lead, and sourced opportunity are defined and agreed with sales before any reporting is built on them.
Step 02
Read campaign and engagement state
Connected Brevo data provides what ran, to whom, and what they did, as an input rather than as a standalone report.
Step 03
Join to downstream outcomes
Campaign activity is joined to CRM outcomes using the agreed definitions, so the answer survives contact with the sales team.
Step 04
Carry context into follow-up
Conversions reach follow-up with the campaign, page, and stated interest attached, so the first reply is specific.
Design decisions
The marketing decisions this connection forces.
Each of these has to be settled before the Brevo workflow is allowed to write anything.
Step 01
Agree the measurement definitions
Write down what counts as a lead, a qualified lead, and a sourced opportunity before connecting Brevo. Most attribution disputes are definitional rather than technical.
Step 02
Carry campaign context into follow-up
The campaign, page, and stated interest should travel with the conversion into the follow-up workflow, so the first reply is specific rather than generic.
Implementation path
How to implement the Brevo workflow.
- 01
Decide which measurement Brevo is authoritative for and which questions must be answered from the CRM instead.
- 02
Write down the lead, MQL, and opportunity definitions and get sales to agree to them before you build reporting.
- 03
Instrument one campaign end to end rather than connecting everything and hoping the picture assembles itself.
- 04
After transactional-failure follow-up works, extend to lifecycle: the moments where delivery succeeded but the customer did not act.
Governance
Controls that matter.
Control 01
Consent, preference, and suppression state is respected as a first-class input, not a downstream filter.
Control 02
Public and brand-facing copy stays under human review before publication or send.
Control 03
Reporting definitions are documented and versioned so a change in the numbers can be explained.
Failure modes
How a Brevo integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Password reset emails stop reaching customers.
Cause
A marketing suppression was applied to a contact and the transactional path was affected.
Fix
Keep the two suppression states distinct in your own logic and never apply a marketing preference to transactional sending.
Symptom 02
Deliverability drops after a volume increase.
Cause
Sending exceeded what the IP was warmed for.
Fix
Ramp volume gradually and monitor bounce and complaint rates as the gate rather than the send count.
Symptom 03
A leaked key sent campaigns.
Cause
One account-wide key covers both marketing and transactional.
Fix
Rotate immediately and restrict where the key is deployed; there is no scoping to fall back on.
What changes at scale
Sending limits and API rate limits are plan-dependent and enforced separately. Growth in volume needs both raised, and hitting either one degrades the other's behaviour.
Examples
What a working Brevo workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Email lifecycle workflows
With Brevo connected, campaign and engagement data can be analyzed alongside pipeline context rather than in isolation, which is what makes the answer actionable rather than descriptive.
Campaign-to-pipeline reporting
A Launch-built dashboard joins Brevo activity with CRM outcomes using agreed definitions, replacing the monthly manual reconciliation.
Limitations and considerations
What to validate before you depend on this.
- Sending limits and dedicated-IP warmup rules apply per plan, so a workflow that increases volume can degrade deliverability before it increases response.
- Blacklisting the wrong channel stops transactional mail — password resets and receipts — while looking like a marketing preference change. Customers then cannot use the product and nobody connects the two.
- When transactional volume is the whole requirement. A dedicated transactional provider gives better delivery visibility without the marketing surface attached.
- Attribution stays a model. Connected data makes it consistent and explainable; it does not make it a single objective truth.
- Platform reporting inside Brevo and workflow reporting will not always match exactly, because they measure different things at different times. Decide which answers which question.
FAQ
Brevo integration questions.
What records does a Brevo integration actually work with?
The primary records are Contact, List, Campaign, Transactional Email, SMS, and Automation. Brevo carries marketing and transactional sending on one contact record, so unsubscribing from marketing must not stop transactional delivery. The two consent states are separate and easy to conflate.
What should the first Brevo workflow be?
Read transactional send outcomes for one lifecycle moment and stage a human follow-up where delivery succeeded but the intended action did not happen.
What will a Brevo integration not do?
It will not make list quality irrelevant. Brevo's cost model rewards sending more; the integration should be reducing sends that have no reason behind them.
What is the main constraint to plan around?
Sending limits and dedicated-IP warmup rules apply per plan, so a workflow that increases volume can degrade deliverability before it increases response.
What changes about a Brevo integration at scale?
Sending limits and API rate limits are plan-dependent and enforced separately. Growth in volume needs both raised, and hitting either one degrades the other's behaviour.
How does authentication work for Brevo?
API key, account-wide and unscoped. Marketing and transactional sending share the same credential, which means a key leaked from a transactional service can send campaigns.
Does Brevo support webhooks, and can they be trusted?
Webhooks cover both marketing and transactional events, configured separately per type. Transactional delivery events are the operationally useful ones, because they reveal failures the application never sees.
What is the risk of writing to Brevo?
Blacklisting the wrong channel stops transactional mail — password resets and receipts — while looking like a marketing preference change. Customers then cannot use the product and nobody connects the two.
When is connecting Brevo the wrong call?
When transactional volume is the whole requirement. A dedicated transactional provider gives better delivery visibility without the marketing surface attached.
What should a Brevo integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Brevo to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can Brevo data be joined to pipeline outcomes?
Yes, provided the lead and opportunity definitions are agreed first. The join is straightforward; the definitions are where these projects usually stall.
Why do the numbers differ from the platform dashboard?
Platform reporting and workflow reporting measure different events over different windows. Decide which system answers which question rather than trying to force them to agree.
Does campaign context survive into follow-up?
It should. The campaign, page, and stated interest travel with the conversion so the first reply is specific rather than a generic acknowledgement.
How this access is governed
What ARIA is allowed to do in Brevo, and who decides.
Connecting Brevo is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.