Learn Mokapen

Brevo — contacts

Connect Brevo to the organization’s contacts. Sync is bidirectional: contacts align between Brevo and Mokapen, with field mapping ready and history imported on the first connection. Later updates follow on their own. This is not the page for sent campaigns: opens and clicks are in the Brevo campaigns guide.

Overview: Integrations.

Requirements

• Brevo account with an API key (in Brevo: SMTP & API → API keys).
• Mokapen Medium plan. Below that plan the button opens the upgrade.
• Permission to work contacts in Mokapen. See Roles and permissions.

Connect

User menu → Integrations → Brevo. Paste the API key and connect. If Brevo replies that the server IP address is not authorized, the key is valid but Brevo’s API security blocks Mokapen. The on-page message shows the IP to add to the Brevo API whitelist. Without that IP, sync does not start, even with the right key.

On the first connection, history starts. From then on, changes travel both ways. The default mapping covers the standard fields: check it before a bulk send, because an empty Mokapen field can overwrite a Brevo attribute that matters to you (language, list, consent), and the other way around.

When this is not the integration

• You need opens and clicks from campaigns already sent. That is Brevo campaigns, another card, with its own API key and the webhook for new events.
• You only want to send a sequence from the CRM. Sequences use Mokapen’s SMTP mailboxes, not Brevo. See Sequences.
• Two Brevo accounts on the same organization. Connect the one that must remain the source of contacts. A second connection on the same perimeter produces duplicates, not a backup.