Integration
Connect Dentally to Mx Technologies
When New Appointment fires in Dentally, your agent runs Add user in Mx Technologies. 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 Dentally and Mx Technologies 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 Dentally can start in Mx Technologies
When New Appointment in Dentally
then Add user in Mx Technologies
When New Invoice in Dentally
then Add account in Mx Technologies
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 Dentally and Mx Technologies
Triggers and actions 4 triggers · 77 actions
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
Action
Add accountCreates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.
Action
Add budgetCreates a budget for a category on an MX user.
Action
Add categoryCreate a custom category for a user.
Action
Add goalCreate a goal for a user.
Action
Add memberCreate a member (connection between a user and a financial institution) to start aggregation.
Action
Add transactionCreates a manual transaction on a manual account belonging to an MX user.
Action
Add userCreates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.
Action
Aggregate memberStarts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently.
Action
Delete accountDelete a manually created account.
Action
Delete budgetDeletes a budget belonging to an MX user.
Action
Delete categoryDelete a custom category.
Action
Delete goalDelete a goal.
Action
Delete memberDelete a member connection.
Action
Delete userDelete a user.
Action
Get accountRead an account's attributes.
Action
Get budgetRetrieves a specific budget for an MX user.
Action
Get institutionRead an institution's attributes.
Action
Get memberRead a member's attributes and connection status.
Action
Get merchantReturns information about a particular merchant, such as its logo, name, and website.
Action
Get transactionRead a transaction's attributes.
Action
Get userRetrieves the attributes of a specific MX user.
Action
List accountsLists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.
Action
List categoriesLists all categories for an MX user, including default and custom categories.
Action
List goalsLists all goals for an MX user.
Action
List institutionsLists financial institutions available through MX, optionally filtered by name, country and supported product.
Action
List membersList all members belonging to a user.
Action
List merchantsLists merchants in the MX system, optionally filtered by a name substring.
Action
List transactionsList all transactions for a user.
Action
Update accountUpdates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata.
Action
Update budgetUpdate a specific budget.
Action
Update categoryUpdate a custom category.
Action
Update goalUpdates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.
Action
Update memberUpdates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.
Action
Update transactionUpdate a transaction's category, description, or other editable attributes.
Action
Update userUpdate a user's attributes.
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 Dentally
Dentally to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Dentally to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Dentally to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Dentally to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Dentally to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Dentally to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Mx Technologies
Felt to Mx TechnologiesCloud-based GIS platform for creating interactive maps and dashboards from geospatial and database data.
HubSpot to Mx TechnologiesHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Mx TechnologiesSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Mx TechnologiesSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Mx TechnologiesGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Mx TechnologiesGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Dentally and Mx Technologies, answered
What can start an automation from Dentally?
Any of Dentally's 4 triggers in the catalog, including New Appointment, New Invoice, New Patient and New Payment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mx Technologies when something happens in Dentally?
Any of Mx Technologies's 35 actions, including Update account, Update budget, Update category and Update goal. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mx Technologies to Dentally?
Mx Technologies has no triggers in the catalog today, so automations start in Dentally. If you need the other direction, ask: your agent reads Mx Technologies's API documentation and adds it.
Do I have to build a connector for Dentally or Mx Technologies?
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 Dentally and Mx Technologies 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.