Brevo integration: sync contacts, trigger and import

Connect Simio with Brevo to sync contacts and consent, import segments, trigger WhatsApp campaigns and keep opt-in status aligned across both platforms.

The Brevo connector lets Simio and your Brevo email marketing account share contacts and consent state in both directions, and lets a Brevo automation trigger a Simio WhatsApp campaign send. This page covers setup, the import flow, and the opt-in sync behavior.

What an admin configures

Setting	Purpose
Brevo API key	Authenticates Simio’s calls to Brevo
Phone field name	Which Brevo contact attribute holds the phone number (defaults to a standard field, but can be renamed to match however the company’s Brevo account is set up)
Opt-in field name	Which Brevo contact attribute should reflect WhatsApp opt-in status (defaults to a standard field name, similarly renameable)

Authorize Simio’s IP address in Brevo

Brevo can restrict API access to a list of authorized IP addresses. When this protection is on, Brevo rejects every API call that comes from an address not on the list, even with a valid API key. Simio then can’t import segments, sync opt-in status, or read your contact attributes.

Add Simio’s outgoing IP address to your Brevo authorized IPs before you save the connector:

Simio outgoing IP address
57.130.18.70

1. Open the authorized IPs settings

   In Brevo, open your account menu and go to Security > Authorized IPs.

2. Add Simio's address

   Click Add a new IP, enter a.b.c.d, and give it a recognizable name such as Simio.

3. Save and test

   Save the entry, then come back to Simio and save the Brevo connector settings.

If you skip this step while Brevo’s IP restriction is on, the connector looks configured but every call fails. Brevo also emails your account admins about the blocked attempt from an unknown IP.

If you’ve turned off IP restriction in Brevo, no action is needed. We still recommend adding Simio’s address so the connector keeps working if someone turns the restriction back on.

Trigger a campaign from a Brevo automation

A Brevo automation can call Simio directly with a contact’s phone number and a target campaign, and Simio enqueues that send. This requires the company to be actively subscribed; unsubscribed companies are rejected.

Import a Brevo segment into Simio

From within campaign scheduling, an admin can pick an existing Brevo segment and pull it into Simio as a usable audience:

1. Request the export

   Simio asks Brevo to prepare an export of that segment’s contacts.

2. Wait for Brevo's callback

   Brevo processes the export in the background and, once ready, calls Simio back with a download link.

3. Simio downloads and tags

   Simio downloads that file, automatically creates a new tag (named with a timestamp) to represent this import batch, and runs it through the normal contact-import pipeline. This is the same pipeline used for a manually uploaded CSV file.

4. Use the audience

   Once complete, the imported contacts (now carrying that new tag) are available to use as a campaign audience, the same as any other tag-based segment.

Brevo columns are automatically translated into Simio’s expected contact fields (contact ID, email, first/last name, phone, opt-in flag) regardless of exact Brevo column naming or file delimiter, so this works without the admin needing to reformat anything on the Brevo side. Each Brevo contact’s own internal Brevo ID is preserved on the resulting Simio contact specifically so opt-in/opt-out status can be synced back to the correct Brevo record afterward (see below). A contact imported through any other route (manual CSV, other connectors) has no such link back to Brevo and will not receive opt-in sync.

Keeping WhatsApp opt-in status in sync with Brevo

Whenever a contact who has a linked Brevo ID opts in or opts out of WhatsApp messaging within Simio (via a consent step in an automation flow), Simio automatically pushes that same opt-in/opt-out status to the corresponding contact record in Brevo, keeping the two systems’ consent state aligned. This only works for contacts that were imported from Brevo (i.e. that carry a Brevo contact ID); it silently does nothing for contacts with no known Brevo link, and requires both an active subscription and a properly configured Brevo connector to fire at all.