Integration
Connect Cliniko to Mercury
When New or updated attendee fires in Cliniko, your agent runs Add customer in Mercury. 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 Cliniko and Mercury 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)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 Cliniko can start in Mercury
When New or updated attendee in Cliniko
then Add customer in Mercury
When New or updated business in Cliniko
then Get invoice in Mercury
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 Mercury
Triggers and actions 17 triggers · 53 actions
Trigger
Cancelled individual appointmentTriggered when an individual appointment is cancelled.
Trigger
New cancelled attendeeTriggered when an attendee is cancelled.
Trigger
New or updated attendeeTriggered when an attendee is created or updated.
Trigger
New or updated businessTriggered when a business is created or updated.
Trigger
New or updated communicationTriggered when a communication is created or updated.
Trigger
New or updated contactTriggered when a contact is created or updated.
Trigger
New or updated daily availabilityTriggered when a daily availability is created or updated.
Trigger
New or updated group appointmentTriggered when a group appointment is created or updated.
Trigger
New or updated individual appointmentTriggered when an individual appointment is created or updated.
Trigger
New or updated invoiceTriggered when an invoice is created or updated.
Trigger
New or updated patientTriggered when a patient is created or updated.
Trigger
New or updated patient caseTriggered when a patient case is created or updated.
Trigger
New or updated practitionerTriggered when a practitioner is created or updated.
Trigger
New or updated treatment notesTriggered when treatment notes is created or updated.
Trigger
Patient added or removed for group appointment in date rangeTriggered when a patient is added or removed for a group appointment within the specified date range.
Trigger
Two-way sync new or updated contactsA 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 patientsA 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 patientArchives a patient. An error will occur if the patient is not found.
Action
Create contactCreates a new contact.
Action
Create patientCreates a new patient.
Action
Find Appointment by Patient IdReturns appointment details for the specified patient if the Patient ID exists.
Action
Find cancelled appointmentSearches for a cancelled appointment. If no matching appointment is found, an error occurs.
Action
Find contact by emailReturns details of the contact having the specified email address. An error occurs if zero or multiple are found.
Action
Find patient by emailReturns 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 BirthFinds the single active patient whose email and date of birth both match, returning the patient ID and the match count.
Action
Get appointmentReturns details of the specified appointment.
Action
Get appointments by practitioner IDReturns appointment details by practitioner ID.
Action
Get appointment typeReturns details of the specified appointment type.
Action
Get appointment type billable itemReturns details for a billable item.
Action
Get billable itemReturns details of the specified billable item.
Action
Get businessReturns details of the specified business.
Action
Get cancelled appointmentReturns details of the specified cancelled appointment.
Action
Get contactReturns details of the specified contact.
Action
Get group appointmentReturns details of the specified group appointment.
Action
Get group appointment attendeesReturns attendee information for the specified group appointment.
Action
Get individual appointment attendeesReturns attendee information for the specified individual appointment.
Action
Get invoiceReturns details of the specified invoice.
Action
Get patientReturns details of the specified patient.
Action
Get patient attachmentReturns a patient attachment from Cliniko, including its filename, file type and description.
Action
Get patient caseReturns details of the specified patient case.
Action
Get patient referral sourceReturns the referral source for the specified patient.
Action
Get practitionerReturns details of the specified practitioner. An error occurs if not found.
Action
Get practitioner availabilitiesReturns availability information for the specified practitioner.
Action
List Appointments in Date RangeReturns every individual appointment that starts within a given time window, with the total count.
Action
List invoices for patient caseEmits all invoice IDs for the specified patient case.
Action
List PatientsReturns Cliniko patients, optionally filtered (e.g. updated after a date) and sorted, with the total count.
Action
Two-way sync add or update a contactAn 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 patientAn 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 contactUpdates a contact.
Action
Update patientUpdates a patient.
Action
Update patient custom fieldUpdates the value of the specified custom field for the specified patient.
Action
Update patient referralSets 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 attachmentUploads a file, such as a PDF, to a patient's record in Cliniko as an attachment.
Action
Add customerCreates a new Accounts Receivable customer in Mercury that you can invoice.
Action
Add internal transferTransfers funds between two Mercury accounts in the same organization and returns the paired debit and credit transactions.
Action
Add recipientCreates a new payment recipient in Mercury, with optional ACH, wire, real-time payment or check details.
Action
Get invoiceReturns the details of a Mercury invoice, including its customer, amount, status, dates and line items.
Action
Get organizationReturns your Mercury organization's details, including legal business name, EIN, DBAs and subscription tier.
Action
Get recipientReturns the details of a Mercury payment recipient, including name, emails, default payment method and routing information.
Action
Get transactionReturns a single Mercury transaction by its ID, including amount, status, counterparty, attachments and related transactions.
Action
List accountsReturns all Mercury bank accounts in your organization, including balances, account and routing numbers, and status.
Action
List account statementsReturns the monthly statements for a Mercury checking or savings account, optionally limited to a date range.
Action
List categoriesReturns the organization's custom expense categories used to classify transactions.
Action
List customersReturns the accounts receivable customers on your Mercury account (up to 1000).
Action
List invoicesReturns the accounts receivable invoices in your Mercury organization, up to 1,000 at a time.
Action
List recipientsReturns the payment recipients saved in your Mercury account (up to 1000).
Action
List transactionsReturns transactions across all Mercury accounts, optionally filtered by date, status, account, card, category or search text.
Action
Send moneySends money from a Mercury account to a saved recipient by ACH, check, domestic wire or real-time payment. Returns the created transaction.
Action
Update recipientUpdates an existing payment recipient's name, contact details and payment routing information.
Action
Update transactionUpdates the note and/or category of an existing Mercury transaction.
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 Cliniko
Cliniko to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Cliniko to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Cliniko to SendGridSendGrid by Twilio — email delivery and marketing platform.
Cliniko to IntercomIntercom is a customer communications platform for support, engagement, and marketing.
Cliniko to FreshdeskFreshdesk is a cloud-based customer support and helpdesk platform.
Cliniko to KlaviyoKlaviyo is a marketing automation platform for email and SMS.
More into Mercury
HubSpot to MercuryHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to MercurySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to MercurySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to MercuryGoogle Sheets
Gmail to MercuryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to MercuryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Cliniko and Mercury, 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 Mercury when something happens in Cliniko?
Any of Mercury's 17 actions, including Send money, Update recipient, Update transaction and Add customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mercury to Cliniko?
Mercury has no triggers in the catalog today, so automations start in Cliniko. If you need the other direction, ask: your agent reads Mercury's API documentation and adds it.
Do I have to build a connector for Cliniko or Mercury?
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 Mercury 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.