Brevo
Turn orders and customer changes into the right Brevo audiences and campaigns, with a person approving what goes out.
27 ways to read, 19 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Brevo, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create companyApproval by rule
- Create contact folderApproval by rule
- List daily transactional email statisticsRead
Example flow
- Brevo · List daily transactional email statisticsDone
- Brevo · Create companyNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Brevo.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Brevo
- Brevo's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Brevo contacts, lists, folders, segments, draft email campaigns, transactional templates, email events and statistics, senders, webhooks and CRM deals, companies and tasks.
Brevo API docs- Source actions
- 27
- Destination actions
- 19
- Data types
- 22
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Companies4
- Create companyDestinationNot retried automaticallyApproval before production
Creates a CRM company with attributes and links to contacts and deals.
- Get companySource
One CRM company with attributes and linked contacts and deals.
- List companiesSourceIncremental
CRM companies with attributes and linked contacts and deals.
- Update companyDestinationProvider duplicate protectionApproval before production
Updates supplied company fields; omitted fields are unchanged.
Contact attributes1
- List contact attributesSource
Contact attributes (custom fields) with category, type and enumeration values.
Contact folders3
- Create contact folderDestinationNot retried automaticallyApproval before production
Creates a contact folder.
- List contact foldersSource
Folders with subscriber counts.
- Rename contact folderDestinationProvider duplicate protectionApproval before production
Renames a contact folder.
Contact list members1
- Add contacts to listDestinationProvider duplicate protectionApproval before production
Adds existing contacts to a list by contact ID or email (up to 150 per call).
Contact lists4
- Create contact listDestinationNot retried automaticallyApproval before production
Creates a list in a folder.
- Get contact listSource
One list with subscriber counts and sent campaign statistics.
- List contact listsSource
Contact lists with subscriber and blocklisted counts.
- Update contact listDestinationProvider duplicate protectionApproval before production
Renames a list or moves it to another folder (one change per call).
Contacts4
- Create contactDestinationNot retried automaticallyApproval before production
Creates a contact with attributes, lists and blocklist flags.
- Get contactSource
One contact by contact ID or EXT_ID, with attributes and list memberships.
- List contactsSourceIncremental
Contacts with attributes, list memberships and blocklist (consent) flags, optionally by list or segment and modified since a date.
- Update contactDestinationProvider duplicate protectionApproval before production
Updates attributes, adds or removes list memberships and sets blocklist flags for a contact.
Customers2
- List CustomersSource
List operation for Customers.
- Upsert CustomersDestinationNexra idempotency keyApproval before production
Upsert operation for Customers.
Deals4
- Create dealDestinationNot retried automaticallyApproval before production
Creates a CRM deal with attributes and links to contacts and companies.
- Get dealSource
One CRM deal with attributes and linked contacts and companies.
- List dealsSourceIncremental
CRM deals with stage, pipeline, amount, attributes and linked contacts and companies.
- Update dealDestinationProvider duplicate protectionApproval before production
Updates supplied deal fields; omitted fields are unchanged.
Domains1
- List sender domainsSource
Sender domains with verification and authentication status.
Email campaigns4
- Create draft email campaignDestinationNot retried automaticallyApproval before production
Creates a classic email campaign as a draft with content, sender and recipients. It is not sent or scheduled.
- Get email campaign statisticsSource
One email campaign with global statistics and per-link clicks.
- List email campaignsSource
Email campaigns with recipients and global statistics.
- Update draft email campaignDestinationProvider duplicate protectionApproval before production
Updates a campaign's content, sender or recipients. Scheduling, sending and status changes are never sent.
Pipelines1
- List deal pipelinesSource
Deal pipelines with their stages.
Segments1
- List segmentsSource
Contact segments with category and last update.
Senders1
- List sendersSource
Sender identities with active status and dedicated IPs.
SMS campaigns1
- List SMS campaignsSource
SMS campaigns with recipients and delivery statistics.
Smtp templates4
- Create transactional templateDestinationNot retried automaticallyApproval before production
Creates a transactional email template. Nothing is sent.
- Get transactional templateSource
One transactional template with its HTML content.
- List transactional templatesSource
Transactional email templates with sender, subject and status.
- Update transactional templateDestinationProvider duplicate protectionApproval before production
Updates a transactional template's content, sender, subject or status.
Task types1
- List task typesSource
CRM task types such as call, email and meeting.
Tasks4
- Create CRM taskDestinationNot retried automaticallyApproval before production
Creates a CRM task linked to contacts, deals or companies.
- Get CRM taskSource
One CRM task.
- List CRM tasksSource
CRM tasks filtered by type, status, due period, assignee or linked record.
- Update CRM taskDestinationProvider duplicate protectionApproval before production
Updates supplied task fields, for example marking it done.
Transactional email events1
- List transactional email eventsSourceIncremental
Unaggregated transactional email events (delivered, opened, clicks, bounces and others) for up to 90 days.
Transactional email reports1
- List daily transactional email statisticsSource
Transactional email requests, deliveries, opens, clicks and bounces per day.
Transactional email statistics1
- Get transactional email statisticsSource
Transactional email totals over a period (up to 90 days), optionally for a tag.
Transactional emails1
- Send transactional emailDestinationNot retried automaticallyApproval before production
Sends one transactional email from a template or HTML content to one or more recipients.
Webhooks1
- List webhooksSource
Transactional, marketing or inbound webhooks with their events and URLs.
Access and limits
- Authentication
- API key
- Plans and access
- All Brevo plans; CRM deals and companies require the Sales Platform features on the account. Transactional email requires a validated sender or domain.
- Test environment
- Free plans allow testing; transactional sends to real recipients count against the daily quota.
- Rate limits
- Per-endpoint hourly and per-second limits by plan (for example transactional email up to 1000 requests per second); HTTP 429.
- Pagination
- limit and offset with count for lists and campaigns; offset for deals; page for companies.
- Provider events
- Transactional, marketing and CRM webhooks. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Contact reads and email-keyed upserts with read-back verification. Requires configured FIRSTNAME/LASTNAME attributes. Blacklist and consent flags are preserved. No campaign sending.
- Transactional email is high risk: Brevo documents no idempotency header, so an uncertain send is never repeated automatically.
- Email campaigns are created and updated as drafts only: Nexra never sends, schedules or changes a campaign's status, and never sends test emails. SMS campaign writes are not implemented.
- No deletes (contacts, lists, folders, templates, CRM records) and no contact imports or exports.
- Contact reads and updates use the contact ID or EXT_ID; email addresses are never placed in URLs, so the transactional event filter by email is not offered.
- Webhook authentication headers and sender domain creator details are not returned.
- Contact create does not update existing contacts (the built-in Upsert customer does); Brevo rejects a duplicate email.
- Updating deal or company links replaces the existing linked IDs.
- Attachments are not sent with transactional email.
Developer reference
- Create the Brevo credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Brevo, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/brevo and the Connections API.