Integration
Connect Brevo and Parseur
When Company Added fires in Brevo, your agent runs Create Document in Parseur, or New Document Export Failed in Parseur to Add or Update Contact in Brevo. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Brevo and Parseur to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Brevo and Parseur can do together
From Brevo to Parseur
When Company Added in Brevo
then Create Document in Parseur
When Company Updated in Brevo
then Create Document From File in Parseur
From Parseur to Brevo
When New Document Export Failed in Parseur
then Add or Update Contact in Brevo
When New Document Not Processed in Parseur
then Send Transactional Email in Brevo
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Brevo and Parseur
Triggers and actions 22 triggers · 23 actions
Trigger
Company AddedTriggers when a company is created in Brevo.
Trigger
Company UpdatedTriggers when a company is updated in Brevo.
Trigger
Contact AddedTriggers when a Brevo contact is added.
Trigger
Contact Subscribed to List (instant)Instant trigger — fires when a contact is added to a list (Brevo marketing webhook event listAddition). Self-registering via the Brevo Create/Delete webhook API.
Trigger
Contact UnsubscribedTriggers when a contact unsubscribes from an email campaign in Brevo.
Trigger
Contact Updated (instant)Instant trigger — fires when a contact is updated (Brevo marketing webhook event contactUpdated). Self-registering via the Brevo Create/Delete webhook API.
Trigger
Deal AddedTriggers when a deal is created in Brevo.
Trigger
Deal Stage UpdatedTriggers when a deal's stage is updated in Brevo.
Trigger
Link ClickedTriggers when a Brevo contact clicks on any link in a Brevo email campaign.
Trigger
Marketing Email DeliveredTriggers when a Brevo campaign marketing email is delivered.
Trigger
Marketing Email Hard BouncedTriggers when a Brevo campaign marketing email is hard bounced.
Trigger
Marketing Email OpenedTriggers when a Brevo campaign marketing email is opened.
Trigger
New Campaign StatusTriggers when the status of a Brevo campaign is updated.
Trigger
Transactional Email DeliveredTriggers when a Brevo transactional email is delivered.
Trigger
Transactional Email Hard BouncedTriggers when a Brevo transactional email is hard bounced.
Trigger
Transactional Email OpenedTriggers when a Brevo transactional email is opened.
Action
Add or Update AssociationsAdds or updates associations to companies, deals or contacts in Brevo.
Action
Add or Update ContactCreates or updates a contact. An attribute you map but leave EMPTY is IGNORED - the stored value is preserved, not deleted. Because of that, this action cannot CLEAR an attribute: to empty one, edit it in Brevo directly. Note an explicit null does not clear on Brevo either.
Action
Delete CompanyDeletes the selected company in Brevo, identified by its company ID.
Action
Delete ContactDeletes the selected contact in Brevo. The contact can be identified by its email address or its contact ID.
Action
Delete DealDeletes the selected deal in Brevo, identified by its deal ID.
Action
Find CompanyFinds companies in Brevo whose name matches the name you supply. Returns every match, up to 50.
Action
Find DealFinds deals in Brevo whose name matches the name you supply. Returns every match, up to 50.
Action
Remove AssociationsRemoves associations between companies, deals, or contacts in Brevo.
Action
Search ContactCheck if a contact exists in Brevo and fetch the contact details. Contact can be found by email, mobile phone number, Brevo contact ID, external ID, Whatsapp ID and landline number.
Action
Send Transactional EmailSends an email from your Brevo account with HTML or plain text content.
Action
Send Transactional SMSSends an transactional SMS from your Brevo account.
Action
Unsubscribe ContactUnsubscribe contact from the list(s) he belong to.
Action
Update ContactUpdates an existing contact by its Brevo contact ID: set attributes, block or unblock email campaigns, and add the contact to or remove it from lists. Only the fields you fill in are changed.
Trigger
New Document Export FailedTriggered when Parseur fails to export a document to its destination.
Trigger
New Document Not ProcessedTriggered when Parseur receives a document it cannot extract data from, so you can follow it up.
Trigger
New Document ProcessedTriggered when Parseur finishes extracting data from a document, with the extracted fields.
Trigger
New Document Processed (With List Items)Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).
Trigger
New MailboxTriggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.
Trigger
New Table Field ProcessedTriggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.
Action
Create DocumentSends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Create Document From FileUploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Delete DocumentDeletes a document from Parseur by its ID.
Action
Delete MailboxDeletes a Parseur mailbox and everything in it. This cannot be undone.
Action
Get DocumentReturns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.
Action
Get MailboxReturns one Parseur mailbox by its ID, with its email address, document counts and settings.
Action
List DocumentsReturns the documents in Parseur, optionally narrowed to one mailbox or one processing status.
Action
List MailboxesReturns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.
Action
Reprocess DocumentSends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.
Action
Update MailboxUpdates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Brevo
Brevo to Base44Base44 is a platform that allows non-technical people to build their own Apps using AI.
Brevo to ClerkClerk is a user authentication and management platform that lets developers add sign-in, profiles, and...
Brevo to Ducks UnlimitedDucks Unlimited publishes its conservation and chapter geodata through an ArcGIS open-data portal.
Brevo to Mistral AIMistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...
Brevo to PrerenderPrerendering service that converts JavaScript-heavy web pages into cached HTML for search engine and AI...
Brevo to The Weather ChannelWeather data API providing current conditions, forecasts, radar, severe weather alerts, and aviation weather.
More into Parseur
HubSpot to ParseurHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ParseurGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ParseurGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ParseurGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ParseurGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ParseurMailchimp marketing automation and email platform.
Questions
Brevo and Parseur, answered
What can start an automation from Brevo?
Any of Brevo's 16 triggers in the catalog, including Company Added, Company Updated, Contact Added and Contact Updated (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Parseur when something happens in Brevo?
Any of Parseur's 10 actions, including Create Document, Create Document From File, Update Mailbox and Get Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Parseur to Brevo?
Yes. When something happens in Parseur, your agent can act in Brevo too. This page covers both directions: Parseur's triggers and Brevo's actions are listed here as well.
Do I have to build a connector for Brevo or Parseur?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Brevo and Parseur without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.