Integration
Connect Brevo to Fatture in Cloud
When something happens in Brevo, your agent does the next thing in Fatture in Cloud. Describe it 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 Fatture in Cloud to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 can start in Fatture in Cloud
When Company Added in Brevo
then Create Cashbook Entry in Fatture in Cloud
When Company Updated in Brevo
then Create Client in Fatture in Cloud
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 Fatture in Cloud
Triggers and actions 16 triggers · 87 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 CompanyCreate a new company or update an existing one 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
Add or Update DealCreate a new deal or update an existing one in Brevo.
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
Event CreateCreate event for selected contact.
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
Create Cashbook EntryCreates a new cashbook entry.
Action
Create ClientCreates a new client in a Fatture in Cloud company.
Action
Create F24Creates a new F24 tax payment record in a Fatture in Cloud company.
Action
Create Issued DocumentCreates a new issued document (invoice, quote, proforma, receipt, delivery note, credit note, order, work report, supplier order or self invoice) in a Fatture in Cloud company.
Action
Create Payment AccountCreates a new payment account.
Action
Create Payment MethodCreates a new payment method.
Action
Create ProductCreates a new product.
Action
Create ReceiptCreates a new receipt.
Action
Create Received DocumentCreates a new document.
Action
Create SupplierCreates a new supplier.
Action
Create Vat TypeCreates a vat type.
Action
Delete Bin Issued DocumentDelete Bin Issued Document
Action
Delete Bin Received DocumentDelete Bin Received Document
Action
Delete Cashbook EntryDeletes the specified cashbook entry.
Action
Delete ClientDeletes the specified client.
Action
Delete F24Removes the specified F24.
Action
Delete Issued DocumentDeletes the specified document.
Action
Delete Issued Document AttachmentRemoves the attachment of the specified document.
Action
Delete Payment AccountDeletes the specified payment account.
Action
Delete Payment MethodDeletes the specified payment method.
Action
Delete ProductDeletes the specified product.
Action
Delete ReceiptDeletes the specified receipt.
Action
Delete Received DocumentDeletes the specified document.
Action
Delete SupplierDeletes the specified supplier.
Action
Delete Vat TypeDeletes the specified vat type.
Action
Get Archive DocumentGets the specified archive document.
Action
Get Bin Issued Documents ListReturns the issued documents currently in the bin.
Action
Get Bin Received Documents ListGet bin issued documents detail
Action
Get Cashbook EntryGets the specified cashbook entry.
Action
Get ClientGets the specified client.
Action
Get F24Gets the specified F24.
Action
Get Issued DocumentGets the specified document.
Action
Get Payment AccountGets the specified payment account.
Action
Get Payment MethodGets the specified payment method.
Action
Get ProductGets the specified product.
Action
Get ReceiptGets the specified receipt.
Action
Get Received DocumentGets the specified document.
Action
Get SupplierGets the specified supplier.
Action
Get Vat TypeGets the specified vat type.
Action
Join Issued DocumentsJoins issued documents.
Action
List Archive DocumentsLists the archive documents.
Action
List Cashbook EntriesLists the cashbook entries.
Action
List ClientsLists the clients.
Action
List F24Lists the F24s.
Action
List Issued DocumentsLists the issued documents.
Action
List Payment AccountsLists the available payment accounts.
Action
List Payment MethodsLists the available payment methods.
Action
List Pending Received DocumentsLists the pending received documents.
Action
List ProductsLists the products.
Action
List ReceiptsLists the receipts.
Action
List Received DocumentsLists the received documents.
Action
List SuppliersLists the suppliers.
Action
List Vat TypesLists the available vat types.
Action
Modify Archive DocumentModifies the specified archive document.
Action
Modify Cashbook EntryModifies the specified cashbook entry.
Action
Modify ClientModifies the specified client.
Action
Modify F24Modifies the specified F24.
Action
Modify Issued DocumentModifies the specified document.
Action
Modify Payment AccountModifies the specified payment account.
Action
Modify Payment MethodModifies the specified payment method.
Action
Modify ProductModifies the specified product.
Action
Modify ReceiptModifies the specified receipt.
Action
Modify Received DocumentModifies the specified document.
Action
Modify SupplierModifies the specified supplier.
Action
Modify Vat TypeModifies the specified vat type.
Action
Recover Issued Document From the BinRecover Issued Document From the Bin
Action
Recover Received Document From the BinRecover Received Document From the Bin
Action
Schedule EmailSchedules the sending of a document by email.
Action
Upload Archive Document AttachmentUploads an attachment destined to an archive document. The actual association between the document and the attachment must be implemented separately, using the returned token.
Action
Upload F24 AttachmentUploads an attachment destined to a F24. The actual association between the document and the attachment must be implemented separately, using the returned token.
Action
Upload Issued Document AttachmentUploads an attachment destined to an issued document. The actual association between the document and the attachment must be implemented separately, using the returned token.
Action
Upload Received Document AttachmentUploads an attachment destined to a received document. The actual association between the document and the attachment must be implemented separately, using the returned token.
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 SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Brevo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Brevo to Google SheetsGoogle Sheets
Brevo to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Brevo to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Brevo to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Fatture in Cloud
HubSpot to Fatture in CloudHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Fatture in CloudSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Fatture in CloudSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Fatture in CloudGoogle Sheets
Gmail to Fatture in CloudGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Fatture in CloudGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Brevo and Fatture in Cloud, 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 Fatture in Cloud when something happens in Brevo?
Any of Fatture in Cloud's 72 actions, including Create Cashbook Entry, Create Client, Create F24 and Create Issued Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fatture in Cloud to Brevo?
Fatture in Cloud has no triggers in the catalog today, so automations start in Brevo. If you need the other direction, ask: your agent reads Fatture in Cloud's API documentation and adds it.
Do I have to build a connector for Brevo or Fatture in Cloud?
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.
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.