Integration
Connect Brevo and Dentally
When Company Added fires in Brevo, your agent runs Get invoice by ID in Dentally, or New Appointment in Dentally 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 Dentally 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Dentally can do together
From Brevo to Dentally
When Company Added in Brevo
then Get invoice by ID in Dentally
When Company Updated in Brevo
then Create an appointment in Dentally
From Dentally to Brevo
When New Appointment in Dentally
then Add or Update Contact in Brevo
When New Invoice in Dentally
then Add or Update Deal 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 Dentally
Triggers and actions 20 triggers · 58 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
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 AppointmentTriggers when a new appointment is booked.
Trigger
New InvoiceTriggers when a new invoice is raised.
Trigger
New PatientTriggers when a new patient is added to the practice.
Trigger
New PaymentTriggers when a new payment is recorded.
Action
Cancel an appointmentCancels the appointment matching `id` for the practice identified by `X-Practice-Id`. The appointment `state` is set to `Cancelled` and `cancelled_at` is recorded.
Action
Create an appointmentCreates a new appointment for the practice identified by `X-Practice-Id`. The appointment location (`site_id`) is determined by the site of the practitioner specified in `practitioner_id`. On success, the newly created appointment is returned in the `data` envelope with a state of `Pending`.
Action
Get appointment by IDReturns the **single appointment** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing appointments.
Action
Get calendar zone by IDReturns the single calendar zone matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing calendar zones.
Action
Get fee by IDReturns the **single fee** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing fees. If no fee exists for that practice and `id`, the API responds with **404**.
Action
Get fee schedule by IDReturns the single fee schedule matching `id` for the practice identified by `X-Practice-Id`. Dentally's user interface in the United Kingdom sometimes calls this a payment plan. The identifier is the same `id` returned when listing fee schedules.
Action
Get invoice by IDReturns the **single invoice** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing invoices.
Action
Get NHS contract by IDReturns the single NHS contract matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing NHS contracts.
Action
Get patient account balanceReturns the account balance for the patient matching `id`, for the practice identified by `X-Practice-Id`. The balance is the account the patient's invoices and payments are posted to. The `id` is the same patient `id` returned when listing patients. Monetary amounts are signed. A negative amount me
Action
Get payment by IDReturns the payment matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing payments. If no payment exists for that practice and `id`, the API responds with 404.
Action
Get practitioner by IDReturns the **single practitioner** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing practitioners.
Action
Get response detailsReturns the details of a **single response communication** to a communication matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when [creating an SMS communication](#operation/send-communication).
Action
Get site by IDReturns the **single site** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing sites.
Action
Get the current practiceReturns the **current practice**: the practice identified by the `X-Practice-Id` header.
Action
Get treatment appointment by IDReturns the **single treatment appointment** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing treatment appointments. If no treatment appointment exists for that practice and `id`, the API responds with **404**.
Action
Get treatment by IDReturns the single treatment matching `id` for the practice identified by `X-Practice-Id`. Treatments are practice-wide. The identifier is the same `id` returned when listing treatments.
Action
Get treatment category by IDReturns the single treatment category matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing treatment categories.
Action
Get treatment plan by IDReturns the **single treatment plan** matching `id` for the practice identified by `X-Practice-Id`. The identifier is the same `id` returned when listing treatment plans. If no treatment plan exists for that practice and `id`, the API responds with **404**.
Action
List allocations for a paymentReturns a **paginated** list of payment allocations for the payment identified by `id` in the path, within the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort. Use `limit` and the `met
Action
List appointment cancellation reasonsReturns a **paginated** list of appointment cancellation reasons for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, latest first (`created_at` descending), then by `id` descending for a stable sort.
Action
List appointment reasonsReturns a **paginated** list of appointment reasons for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, latest first (`created_at` descending), then by `id` descending for a stable sort.
Action
List appointmentsReturns a **paginated** list of appointments for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, latest first (`created_at` descending), then by `id` descending for a stable sort.
Action
List calendar zonesReturns a paginated list of calendar zones for the practice identified by `X-Practice-Id`. A calendar zone is one occurrence of a scheduled, recurring block of diary time reserved for a specific purpose, for a practitioner or a room.
Action
List feesReturns a **paginated** list of fees for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort. Optional query parameters allow filtering by fee schedule, treatment, and created/updated
Action
List fee schedulesReturns a paginated list of fee schedules for the practice identified by `X-Practice-Id`. Dentally's user interface in the United Kingdom sometimes calls these payment plans.
Action
List invoice itemsReturns a **paginated** list of invoice items for the invoice identified by `id` in the path, within the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.
Action
List invoicesReturns a **paginated** list of invoices for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, most recent created first (`created_at` descending), then by `id` descending for a stable sort.
Action
List NHS contractsReturns a paginated list of NHS contracts for the practice identified by `X-Practice-Id`.
Action
List patientsReturns a paginated list of patients for a practice.
Action
List paymentsReturns a paginated list of payments for the practice identified by `X-Practice-Id`. Results are ordered by creation time, newest first (`created_at` descending), then by `id` descending for a stable sort. Use `limit` and the `meta.cursor` value from the response to retrieve further pages.
Action
List practitioner availabilitiesReturns a **paginated** list of **availability slots** for one or more practitioners.
Action
List practitionersReturns a **paginated** list of practitioners for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.
Action
List rota schedule historiesReturns a **paginated** list of **snapshot rota days** for the practitioner identified by `id` in the path. Each row describes the effective scheduled working hours and breaks for a single calendar date, as captured from the practice rota (including overrides that were active when the snapshot was t
Action
List sitesReturns a **paginated** list of all sites for the practice identified by `X-Practice-Id`. Use this to discover locations where the practice operates, including addresses, contact details, and opening hours.
Action
List sundriesSundries are non-treatment items, such as toothbrushes or other products, that a practice sells and adds to invoices. Returns a **paginated** list of sundries for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id
Action
List treatment appointmentsReturns a **paginated** list of treatment appointments for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.
Action
List treatment categoriesReturns a **paginated** list of treatment categories for the practice identified by `X-Practice-Id`. Treatment categories are the folders a practice uses to group its treatment catalogue.
Action
List treatment plan itemsReturns a **paginated** list of treatment plan items for the treatment plan identified by `id` in the path, within the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.
Action
List treatment plansReturns a **paginated** list of treatment plans for the practice identified by `X-Practice-Id`. Results are ordered by **creation time**, newest first (`created_at` descending), then by `id` descending for a stable sort.
Action
List treatmentsReturns a **paginated** list of treatments for the practice identified by `X-Practice-Id`. Treatments are the practice-level catalogue of procedures that can be assigned to a patient treatment plan.
Action
Search patientsReturns a paginated list of patients for a practice, with optional filters.
Action
Update an appointmentUpdates the appointment matching `id` for the practice identified by `X-Practice-Id`. Only the fields provided in the request body will be modified; omitted fields remain unchanged. If no appointment exists for that practice and `id`, the API responds with **404**. When `reason_id` is provided, it m
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 PlentymarketsCloud e-commerce ERP that manages multichannel orders, inventory, product data, and marketplace listings...
Brevo to PrerenderPrerendering service that converts JavaScript-heavy web pages into cached HTML for search engine and AI...
More into Dentally
ActiveCampaign to DentallyActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to DentallyOrganize anything with Airtable, a modern database created for everyone.
Asana to DentallyAsana is a collaborative information manager for workspace.
ClickUp to DentallyClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Calendly to DentallyCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Capsule CRM to DentallyCapsule is an online hosted CRM system for individuals, small businesses and sales teams wanting a simple...
Questions
Brevo and Dentally, 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 Dentally when something happens in Brevo?
Any of Dentally's 42 actions, including Create an appointment, Update an appointment, Get appointment by ID and Get calendar zone by ID. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Dentally to Brevo?
Yes. When something happens in Dentally, your agent can act in Brevo too. This page covers both directions: Dentally's triggers and Brevo's actions are listed here as well.
Do I have to build a connector for Brevo or Dentally?
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 Dentally 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.