--- title: "Connect Cliniko and Lokalise - APIANT.ai" description: "When \"New or updated attendee\" fires in Cliniko, your agent runs \"Create a Task\" in Lokalise." canonical: "https://apiant.ai/connect/cliniko-to-lokalise" --- # Connect Cliniko and Lokalise When **New or updated attendee** fires in [Cliniko](https://apiant.ai/connections/cliniko), your agent runs **Create a Task** in [Lokalise](https://apiant.ai/connections/lokalise), or **Contributor Added** in Lokalise to **Create contact** in Cliniko. Describe the whole flow and it is built, tested on every scenario and kept running. Cliniko **17** triggers Cliniko **36** actions Lokalise **16** triggers Lokalise **26** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Cliniko and Lokalise to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Cliniko and Lokalise can do together ### From Cliniko to Lokalise - When **New or updated attendee** in Cliniko then **Create a Task** in Lokalise - When **New or updated business** in Cliniko then **Create Comment** in Lokalise ### From Lokalise to Cliniko - When **Contributor Added** in Lokalise then **Create contact** in Cliniko - When **Key Added** in Lokalise then **Update contact** in Cliniko 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 Cliniko and Lokalise ## Triggers and actions 33 triggers · 62 actions - Trigger **Cancelled individual appointment** Triggered when an individual appointment is cancelled. - Trigger **New cancelled attendee** Triggered when an attendee is cancelled. - Trigger **New or updated attendee** Triggered when an attendee is created or updated. - Trigger **New or updated business** Triggered when a business is created or updated. - Trigger **New or updated communication** Triggered when a communication is created or updated. - Trigger **New or updated contact** Triggered when a contact is created or updated. - Trigger **New or updated daily availability** Triggered when a daily availability is created or updated. - Trigger **New or updated group appointment** Triggered when a group appointment is created or updated. - Trigger **New or updated individual appointment** Triggered when an individual appointment is created or updated. - Trigger **New or updated invoice** Triggered when an invoice is created or updated. - Trigger **New or updated patient** Triggered when a patient is created or updated. - Trigger **New or updated patient case** Triggered when a patient case is created or updated. - Trigger **New or updated practitioner** Triggered when a practitioner is created or updated. - Trigger **New or updated treatment notes** Triggered when treatment notes is created or updated. - Trigger **Patient added or removed for group appointment in date range** Triggered when a patient is added or removed for a group appointment within the specified date range. - Trigger **Two-way sync new or updated contacts** A trigger for two-way syncing new and updated contacts, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping. - Trigger **Two-way sync new or updated patients** A trigger for two-way syncing new and updated patients, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping. - Action **Archive patient** Archives a patient. An error will occur if the patient is not found. - Action **Create contact** Creates a new contact. - Action **Create patient** Creates a new patient. - Action **Find Appointment by Patient Id** Returns appointment details for the specified patient if the Patient ID exists. - Action **Find cancelled appointment** Searches for a cancelled appointment. If no matching appointment is found, an error occurs. - Action **Find contact by email** Returns details of the contact having the specified email address. An error occurs if zero or multiple are found. - Action **Find patient by email** Returns details of the patient having the specified email address. An error occurs if zero or multiple are found. - Action **Find Patient by Email and Date of Birth** Finds the single active patient whose email and date of birth both match, returning the patient ID and the match count. - Action **Get appointment** Returns details of the specified appointment. - Action **Get appointments by practitioner ID** Returns appointment details by practitioner ID. - Action **Get appointment type** Returns details of the specified appointment type. - Action **Get appointment type billable item** Returns details for a billable item. - Action **Get billable item** Returns details of the specified billable item. - Action **Get business** Returns details of the specified business. - Action **Get cancelled appointment** Returns details of the specified cancelled appointment. - Action **Get contact** Returns details of the specified contact. - Action **Get group appointment** Returns details of the specified group appointment. - Action **Get group appointment attendees** Returns attendee information for the specified group appointment. - Action **Get individual appointment attendees** Returns attendee information for the specified individual appointment. - Action **Get invoice** Returns details of the specified invoice. - Action **Get patient** Returns details of the specified patient. - Action **Get patient attachment** Returns a patient attachment from Cliniko, including its filename, file type and description. - Action **Get patient case** Returns details of the specified patient case. - Action **Get patient referral source** Returns the referral source for the specified patient. - Action **Get practitioner** Returns details of the specified practitioner. An error occurs if not found. - Action **Get practitioner availabilities** Returns availability information for the specified practitioner. - Action **List Appointments in Date Range** Returns every individual appointment that starts within a given time window, with the total count. - Action **List invoices for patient case** Emits all invoice IDs for the specified patient case. - Action **List Patients** Returns Cliniko patients, optionally filtered (e.g. updated after a date) and sorted, with the total count. - Action **Two-way sync add or update a contact** An action for two-way syncing new and updated contacts, with enhanced on-the-fly mapping using contact email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping. - Action **Two-way sync add or update a patient** An action for two-way syncing new and updated patients, with enhanced on-the-fly mapping using patient email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping. - Action **Update contact** Updates a contact. - Action **Update patient** Updates a patient. - Action **Update patient custom field** Updates the value of the specified custom field for the specified patient. - Action **Update patient referral** Sets or changes a patient's referral source. Choose the referral source type; supply a Referrer ID only for types that take one (e.g. Patient or Contact). - Action **Upload patient attachment** Uploads a file, such as a PDF, to a patient's record in Cliniko as an attachment. - Trigger **Contributor Added** Triggers when a new contributor is added to a Lokalise project. - Trigger **Contributor Removed** Triggers when a contributor is removed from the selected Lokalise project. - Trigger **Key Added** Triggers 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 Added** Triggers when someone adds a comment to a translation key in a Lokalise project. - Trigger **Key Modified** Triggers when a translation key is modified in a Lokalise project, either individually or in bulk (renames, tag changes, file assignments, hiding). - Trigger **Key Removed** Triggers 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 Added** Triggers when one or more languages are added to a Lokalise project, firing once for each language added. - Trigger **Language Removed** Triggers when a language is removed from a Lokalise project. - Trigger **Poll Tasks** Triggers when a new task is created in a Lokalise project. - Trigger **Project Exported** Triggers when translation files are downloaded (exported) from a Lokalise project. - Trigger **Project Imported** Triggers when a translation file is uploaded to a Lokalise project. Fires once per uploaded file. - Trigger **Project Snapshot** Triggers when a snapshot is taken of the selected Lokalise project. - Trigger **Task Created** Triggers when a new translation or review task is created in a Lokalise project. - Trigger **Task Deleted** Triggers when a task is deleted in a Lokalise project. - Trigger **Translation Reviewed** Triggers when a translation is marked or unmarked as reviewed in a Lokalise project, individually or in bulk. - Trigger **Translation Updated** Triggers 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 Contributor** Adds a contributor to a Lokalise project, inviting them by email with the chosen languages and permissions. - Action **Add Languages** Adds one or more languages to a Lokalise project, optionally overriding each language's code, name and plural forms. - Action **Create a Key** Creates a new translation key in a Lokalise project, optionally with its translations, tags, comments and screenshots, and returns the new key. - Action **Create a Task** Creates a translation, review or automatic-translation task in a Lokalise project for the chosen keys and languages. - Action **Create Comment** Adds a comment to a translation key in a Lokalise project. - Action **Create Project** Creates a new Lokalise project in your team, optionally with its languages, base language and project type. Returns the created project. - Action **Create Snapshot** Creates a snapshot of a Lokalise project, saving its current state so it can be restored later. - Action **Delete a Key** Deletes a key, with its translations, from a Lokalise project. - Action **Delete a Language** Removes a language from a Lokalise project. - Action **Delete a Task** Deletes a task from a Lokalise project. - Action **Download Files** Exports a Lokalise project's translation files as a.zip bundle and returns the download URL of the bundle. - Action **List All Orders** Returns all translation orders placed under a Lokalise team. - Action **List All Tasks** Returns the tasks in a Lokalise project, optionally filtered by title or status. - Action **List All Translations** Returns 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 Languages** Returns the languages set up in a Lokalise project, with each language's code, name, direction and plural forms. - Action **List Snapshots** Returns the snapshots saved for a Lokalise project, with each snapshot's title and creation details. - Action **Remove Contributor** Removes a contributor from a Lokalise project. - Action **Retrieve a Comment** Returns a single comment left on a key in a Lokalise project, including its text, author and when it was added. - Action **Retrieve a Contributor** Returns a contributor of a Lokalise project, including their email, name, role flags, languages and permissions. - Action **Retrieve a Key** Returns one translation key from a Lokalise project, including its names, description, platforms, tags, comments, screenshots and translations. - Action **Retrieve a Task** Returns a Lokalise task, including its status, progress, due date and the languages and assignees it covers. - Action **Retrieve Project** Returns a Lokalise project's details, including its name, type, base language, settings and translation statistics. - Action **Update a Key** Updates an existing key in a Lokalise project, such as its name, description, platforms, tags or flags, and returns the updated key. - Action **Update a Translation** Updates the text and review flags of a translation in a Lokalise project. - Action **Update Language** Updates a language in a Lokalise project, changing its code, name or plural forms. - Action **Upload File** Uploads a localization file to a Lokalise project and queues it for import. Returns the queued import process so you can follow its status. ## Each app on its own - [ **Cliniko** Cliniko is a practice management platform — manage patients, appointments, invoices, contacts, and...](https://apiant.ai/connections/cliniko) - [ **Lokalise** Lokalise is a translation management tool that lets you structure and automate workflows while encouraging...](https://apiant.ai/connections/lokalise) Reviews ## What our customers say ## More from Cliniko - [ **Cliniko to JIRA** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/cliniko-to-jira) - [ **Cliniko to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/cliniko-to-zoom) - [ **Cliniko to SendGrid** SendGrid by Twilio — email delivery and marketing platform.](https://apiant.ai/connect/cliniko-to-sendgrid) - [ **Cliniko to Intercom** Intercom is a customer communications platform for support, engagement, and marketing.](https://apiant.ai/connect/cliniko-to-intercom) - [ **Cliniko to Freshdesk** Freshdesk is a cloud-based customer support and helpdesk platform.](https://apiant.ai/connect/cliniko-to-freshdesk) - [ **Cliniko to Klaviyo** Klaviyo is a marketing automation platform for email and SMS.](https://apiant.ai/connect/cliniko-to-klaviyo) ## More into Lokalise - [ **HubSpot to Lokalise** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-lokalise) - [ **Google Sheets to Lokalise** Google Sheets](https://apiant.ai/connect/google-sheets-to-lokalise) - [ **Gmail to Lokalise** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-lokalise) - [ **Google Calendar to Lokalise** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-lokalise) - [ **Google Drive to Lokalise** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-lokalise) - [ **ActiveCampaign to Lokalise** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-lokalise) Questions ## Cliniko and Lokalise, answered ### ### What can start an automation from Cliniko? Any of Cliniko's 17 triggers in the catalog, including New cancelled attendee, New or updated attendee, New or updated business and New or updated communication. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Lokalise when something happens in Cliniko? 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 Cliniko? Yes. When something happens in Lokalise, your agent can act in Cliniko too. This page covers both directions: Lokalise's triggers and Cliniko's actions are listed here as well. ### ### Do I have to build a connector for Cliniko 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 Cliniko 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.