Integration
Connect Dentally and Lokalise
When New Appointment fires in Dentally, your agent runs Create a Task in Lokalise, or Contributor Added in Lokalise to Get invoice by ID in Dentally. 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 Lokalise 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 and Lokalise can do together
From Dentally to Lokalise
When New Appointment in Dentally
then Create a Task in Lokalise
When New Invoice in Dentally
then Create Comment in Lokalise
From Lokalise to Dentally
When Contributor Added in Lokalise
then Get invoice by ID in Dentally
When Key Added in Lokalise
then Create an appointment in Dentally
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 Lokalise
Triggers and actions 20 triggers · 68 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
Trigger
Contributor AddedTriggers when a new contributor is added to a Lokalise project.
Trigger
Contributor RemovedTriggers when a contributor is removed from the selected Lokalise project.
Trigger
Key AddedTriggers when a new translation key is added to a Lokalise project, whether individually or in bulk (import, API or bulk action). Fires once per added key.
Trigger
Key Comment AddedTriggers when someone adds a comment to a translation key in a Lokalise project.
Trigger
Key ModifiedTriggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding).
Trigger
Key RemovedTriggers when one or more translation keys are removed from a Lokalise project, whether deleted individually, in bulk, through the API, or moved to another project. Fires once per removed key.
Trigger
Language AddedTriggers when one or more languages are added to a Lokalise project, firing once for each language added.
Trigger
Language RemovedTriggers when a language is removed from a Lokalise project.
Trigger
Poll TasksTriggers when a new task is created in a Lokalise project.
Trigger
Project ExportedTriggers when translation files are downloaded (exported) from a Lokalise project.
Trigger
Project ImportedTriggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file.
Trigger
Project SnapshotTriggers when a snapshot is taken of the selected Lokalise project.
Trigger
Task CreatedTriggers when a new translation or review task is created in a Lokalise project.
Trigger
Task DeletedTriggers when a task is deleted in a Lokalise project.
Trigger
Translation ReviewedTriggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk.
Trigger
Translation UpdatedTriggers when a translation is changed in the selected Lokalise project, either one at a time or several at once through a bulk action, file upload or the API.
Action
Add ContributorAdds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions.
Action
Add LanguagesAdds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms.
Action
Create a KeyCreates a new translation key in a Lokalise project, optionally with its translations, tags, comments and screenshots, and returns the new key.
Action
Create a TaskCreates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages.
Action
Create CommentAdds a comment to a translation key in a Lokalise project.
Action
Create ProjectCreates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project.
Action
Create SnapshotCreates a snapshot of a Lokalise project, saving its current state so it can be restored later.
Action
Delete a KeyDeletes a key, with its translations, from a Lokalise project.
Action
Delete a LanguageRemoves a language from a Lokalise project.
Action
Delete a TaskDeletes a task from a Lokalise project.
Action
Download FilesExports a Lokalise project's translation files as a .zip bundle and returns the download URL of the bundle.
Action
List All OrdersReturns all translation orders placed under a Lokalise team.
Action
List All TasksReturns the tasks in a Lokalise project, optionally filtered by title or status.
Action
List All TranslationsReturns the translation items of a Lokalise project (one row per key and language), optionally filtered by language, review status, QA issues or task.
Action
List Project LanguagesReturns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms.
Action
List SnapshotsReturns the snapshots saved for a Lokalise project, with each snapshot's title and creation details.
Action
Remove ContributorRemoves a contributor from a Lokalise project.
Action
Retrieve a CommentReturns a single comment left on a key in a Lokalise project, including its text, author and when it was added.
Action
Retrieve a ContributorReturns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions.
Action
Retrieve a KeyReturns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations.
Action
Retrieve a TaskReturns a Lokalise task, including its status, progress, due date and the languages and assignees it covers.
Action
Retrieve ProjectReturns a Lokalise project's details, including its name, type, base language, settings and translation statistics.
Action
Update a KeyUpdates an existing key in a Lokalise project, such as its name, description, platforms, tags or flags, and returns the updated key.
Action
Update a TranslationUpdates the text and review flags of a translation in a Lokalise project.
Action
Update LanguageUpdates a language in a Lokalise project, changing its code, name or plural forms.
Action
Upload FileUploads a localization file to a Lokalise project and queues it for import. Returns the queued import process so you can follow its status.
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 Lokalise
HubSpot to LokaliseHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LokaliseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LokaliseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LokaliseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LokaliseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LokaliseActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Dentally and Lokalise, 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 Lokalise when something happens in Dentally?
Any of Lokalise's 26 actions, including Create a Key, Create a Task, Create Comment and Create Project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Lokalise to Dentally?
Yes. When something happens in Lokalise, your agent can act in Dentally too. This page covers both directions: Lokalise's triggers and Dentally's actions are listed here as well.
Do I have to build a connector for Dentally or Lokalise?
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 Lokalise 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.