How to integrate Unify with Brevo
To integrate Unify with Brevo, send a Play webhook to the Contacts API with an api-key header and a mapped email address. Add only attributes that already exist in the Brevo account. Decide whether existing contacts may be updated, and keep list enrollment and messaging eligibility separate from the act of storing a contact.[1][3]
- Connection
- Via webhook
- Customer engagement
- Tool
- Brevo
- Brevo contact
- Data flow
- Unify → Brevo
- JSON payload
At a glance
- Choose the contact email and its owner
- Map only existing attributes with compatible types
- Decide whether this feed may change existing contacts
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
A contact database is useful when its fields retain a clear meaning. Decide which team owns the email identity and which fields another process may change. Preserve subscription and suppression decisions through a separate, explicit process so a new prospect selection does not accidentally change someone’s messaging status.
A good fit when
Teams already using Brevo with clear contact ownership and a defined downstream process.
Reconsider the plan when
If the objective is only sales sequencing, compare the need for another contact store with the existing Unify workflow.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Identity | Choose the contact email and its owner |
| Fields | Map only existing attributes with compatible types |
| Updates | Decide whether this feed may change existing contacts |
| Enrollment | Treat list and messaging decisions as a separate step |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Prepare contact data for review
Operations needs selected contact identity available in Brevo.
Start with a narrow contact write before adding list rules.
- Map a fictional email
- Create and inspect the contact
- Review the next action with the process owner
Protect established contact preferences
A selected person is already in Brevo.
Limit the feed to fields it is allowed to maintain.
- Review the existing contact
- Choose update behavior and writable fields
- Test without changing subscription decisions
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
The intended contact data is stored with the chosen existing-contact behavior.
Inspect identity, attribute values, and any unintended list or automation effects. Contact persistence is not proof of consent or a delivered campaign.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Brevo.
Does this automatically send email?
The operation stores a contact; this article does not configure a send action.[3]
Can I update a contact in the same request?
updateEnabled controls whether the create request can update an existing contact.[3]
Can I invent an attribute name in the JSON?
Confirm that the attribute exists and uses the expected data type.[4]
Does a prospect selection establish consent?
This handoff only carries selected data. Establish messaging eligibility in your own intake process before enrollment.[1]
Can I read the Brevo contact ID later in the Play?
Unify does not pass webhook response bodies into later steps.[2]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- The contact write does not establish messaging eligibility
- Attribute and automation behavior depends on the Brevo account
- The sample deliberately omits list enrollment and forced merging
- No live Brevo contact or campaign was created
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Brevo workflow.
Technical setup reference
References and requirements for the Brevo connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action
- A Brevo API key and reviewed contact attributes
- A policy for existing contacts and any later list enrollment
Choose update behavior
The sample leaves updateEnabled false. Turn it on only when this feed is allowed to change the supplied fields on an existing contact. Do not enable forceMerge as a generic duplicate fix.[3]
Review audience behavior separately
The sample does not include listIds. Inspect any existing automations before adding contacts to lists, and establish messaging eligibility through your actual process.[3]
Request configuration
- Method
POST- URL pattern
https://api.brevo.com/v3/contacts- Headers
Content-Type: application/jsonapi-key: YOUR_BREVO_API_KEY- Authentication
- Set api-key: YOUR_BREVO_API_KEY as a request header. Keep the key out of the JSON body.
Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]
Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.
Example handoff payload
Start with a fictional prospect. Validate the resolved values before using a real record.
Inspect the sample payload and field mapping
{
"email": "avery@example.com",
"updateEnabled": false
}Fictional data. Replace sample values before using a real Play.
Fictional contact. Existing-contact updates, attribute additions, and list enrollment require deliberate account-specific choices. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[2][3]
| Payload field | Value to send |
|---|---|
email | Map the intended contact email and inspect the preview |
The minimal body uses email and an explicit update policy. Extend attributes only with names and types that exist in your Brevo account; do not infer opt-in from presence in a Unify audience.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
An existing email is rejected
Review updateEnabled and decide whether updating that contact is actually intended.[3]
An attribute is missing
Check the account’s attribute name and data type against the submitted value.[4]
A campaign behaves unexpectedly
Review list assignment and the receiving account’s automation rules independently of the contact write.[3]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
