Integration
Connect Cliniko and SQL Server
When Cancelled individual appointment fires in Cliniko, your agent runs Add Row in SQL Server, or New or Updated Row in SQL Server to Create contact in Cliniko. 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 SQL Server 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)Cliniko holds the patients, appointments and invoices; SQL Server holds the reporting and billing tables the rest of the practice works from. Joining them means a new row in SQL Server can become a Cliniko patient, and a cancelled appointment or new invoice in Cliniko can update the matching rows in your database. The agent builds it, tests every scenario and keeps it running.
Example flows
What Cliniko and SQL Server can do together
From Cliniko to SQL Server
When Cancelled individual appointment in Cliniko
then Add Row in SQL Server
From SQL Server to 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 SQL Server
Triggers and actions 21 triggers · 43 actions
- Cancelled individual appointment
Triggered when an individual appointment is cancelled.
- New cancelled attendee
Triggered when an attendee is cancelled.
- New or updated attendee
Triggered when an attendee is created or updated.
- New or updated business
Triggered when a business is created or updated.
- New or updated communication
Triggered when a communication is created or updated.
- New or updated contact
Triggered when a contact is created or updated.
- New or updated daily availability
Triggered when a daily availability is created or updated.
- New or updated group appointment
Triggered when a group appointment is created or updated.
- New or updated individual appointment
Triggered when an individual appointment is created or updated.
- New or updated invoice
Triggered when an invoice is created or updated.
- New or updated patient
Triggered when a patient is created or updated.
- New or updated patient case
Triggered when a patient case is created or updated.
- New or updated practitioner
Triggered when a practitioner is created or updated.
- New or updated treatment notes
Triggered when treatment notes is created or updated.
- 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.
- 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.
- 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.
- Archive patient
Archives a patient. An error will occur if the patient is not found.
- Create contact
Creates a new contact.
- Create patient
Creates a new patient.
- Find Appointment by Patient Id
Returns appointment details for the specified patient if the Patient ID exists.
- Find cancelled appointment
Searches for a cancelled appointment. If no matching appointment is found, an error occurs.
- Find contact by email
Returns details of the contact having the specified email address. An error occurs if zero or multiple are found.
- Find patient by email
Returns details of the patient having the specified email address. An error occurs if zero or multiple are found.
- 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.
- Get appointment
Returns details of the specified appointment.
- Get appointments by practitioner ID
Returns appointment details by practitioner ID.
- Get appointment type
Returns details of the specified appointment type.
- Get appointment type billable item
Returns details for a billable item.
- Get billable item
Returns details of the specified billable item.
- Get business
Returns details of the specified business.
- Get cancelled appointment
Returns details of the specified cancelled appointment.
- Get contact
Returns details of the specified contact.
- Get group appointment
Returns details of the specified group appointment.
- Get group appointment attendees
Returns attendee information for the specified group appointment.
- Get individual appointment attendees
Returns attendee information for the specified individual appointment.
- Get invoice
Returns details of the specified invoice.
- Get patient
Returns details of the specified patient.
- Get patient attachment
Returns a patient attachment from Cliniko, including its filename, file type and description.
- Get patient case
Returns details of the specified patient case.
- Get patient referral source
Returns the referral source for the specified patient.
- Get practitioner
Returns details of the specified practitioner. An error occurs if not found.
- Get practitioner availabilities
Returns availability information for the specified practitioner.
- List Appointments in Date Range
Returns every individual appointment that starts within a given time window, with the total count.
- List invoices for patient case
Emits all invoice IDs for the specified patient case.
- List Patients
Returns Cliniko patients, optionally filtered (e.g. updated after a date) and sorted, with the total count.
- 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.
- 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.
- Update contact
Updates a contact.
- Update patient
Updates a patient.
- Update patient custom field
Updates the value of the specified custom field for the specified patient.
- 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).
- Upload patient attachment
Uploads a file, such as a PDF, to a patient's record in Cliniko as an attachment.
- New or Updated Row
Triggers when a new row is added or modified.
- New or Updated Row (Custom Query)
Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.
- New Row
Triggers when you add a new row.
- New Table
Fires when a new table appears in the connected SQL Server database.
- Add Row
Add one row to a table on the connected SQL Server database.
- Delete Row
Delete the rows in a table whose chosen column equals a value.
- Find Row
Find the first row in a table whose chosen column matches a value.
- Find Rows via Custom Query
Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches.
- Find Row via Custom Query
Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
- Run Custom Statement
Runs a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.
- Update Row
Change column values on every row of a table whose chosen column matches a value.
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 SQL Server
HubSpot to SQL ServerHubSpot is your all-in-one stop for all of your marketing software needs.
Slack to SQL ServerSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailchimp to SQL ServerMailchimp marketing automation and email platform.
Shopify to SQL ServerShopify is a commerce platform for online stores and retail point-of-sale.
QuickBooks Online to SQL ServerQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pipedrive to SQL ServerPipedrive is a sales CRM and pipeline management tool.
Questions
Cliniko and SQL Server, answered
Can a patient created in Cliniko update an existing row in SQL Server instead of adding a duplicate?
Yes — the agent can use Find Row to look up the matching row by a column such as patient email, then use Update Row to change the values on it. If no row matches, it can add one instead.
Can I use my own SQL to decide when something happens in Cliniko?
Yes — the New or Updated Row (Custom Query) trigger fires for each new or changed row returned by a SELECT statement you write. From there the agent can create a patient, update a patient, or set a patient custom field in Cliniko.
What can start an automation from Cliniko?
Any of Cliniko's 17 triggers in the catalog, including Cancelled individual appointment, New or updated invoice, New or updated practitioner and New cancelled attendee. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SQL Server when something happens in Cliniko?
Any of SQL Server's 7 actions, including Add Row, Run Custom Statement, Update Row and Find Row. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SQL Server to Cliniko?
Yes. When something happens in SQL Server, your agent can act in Cliniko too. This page covers both directions: SQL Server's triggers and Cliniko's actions are listed here as well.
Do I have to build a connector for Cliniko or SQL Server?
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 SQL Server 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.