Integration
Connect Cliniko and COR
When New or updated attendee fires in Cliniko, your agent runs Create Invoice in COR, or Create Brand in COR 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 COR 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 and COR can do together
From Cliniko to COR
When New or updated attendee in Cliniko
then Create Invoice in COR
When New or updated business in Cliniko
then Create Task in COR
From COR to Cliniko
When Create Brand in COR
then Create contact in Cliniko
When Create Client in COR
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 COR
Triggers and actions 29 triggers · 60 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.
Trigger
Create BrandTriggers when a new brand is created in COR.
Trigger
Create ClientTriggers when a new client is created in COR.
Trigger
Create HourTriggers when a new time entry is logged in COR.
Trigger
Create InvoiceTriggers when a new transaction is recorded in COR. COR has no separate invoice record, so this watches all transactions, invoices included; use the type field to tell them apart.
Trigger
Create ProductTriggers when a new product is created in COR.
Trigger
Create ProjectTriggers when a new project is created in COR.
Trigger
Create TaskTriggers when a new task is created in COR. Returns the new task's details.
Trigger
Create UserTriggers when a new user is created in COR.
Trigger
Updated ClientTriggers when an existing client is changed in COR.
Trigger
Updated ProjectTriggers when an existing project is updated in COR.
Trigger
Updated TaskTriggers when a task is changed, such as a new title, status, priority or deadline. Also fires when a new task appears.
Trigger
Updated UserTriggers when a user in COR is created or changed, such as their name, email, role, position or labels.
Action
Add brandCreates a new brand under a client in COR.
Action
Add teamCreates a new team in COR with a name and, optionally, a description and workspace. Returns the team that was created.
Action
Create ClientCreates a new client in COR with its company details and primary contact, and returns the new client's id.
Action
Create FeeCreates a fee for a client in COR, with its name, estimate and work order, and optional details such as dates, status and currency. Returns the new fee.
Action
Create HourLogs a time entry against a task in COR and returns the new entry's id.
Action
Create InvoiceCreates an invoice (a COR transaction) for the given date, total and currency, optionally linked to a client, and returns the new transaction.
Action
Create ProjectCreates a new project for a client in COR and returns the created project.
Action
Create TaskCreates a new task in COR, optionally within a project, and returns the created task.
Action
Delete ProjectDeletes a project in COR by its ID.
Action
Delete taskDeletes a task in COR by its ID.
Action
Find clients by nameReturns the clients whose name matches the specified name.
Action
Find projects by nameReturns the COR projects whose name matches the name you search for, including each project's client, project manager, status and budget details.
Action
Get clientReturns a single COR client by its id, including its business name, contact details, website and description.
Action
Get projectReturns a single COR project by its id, including its client, project manager, dates, status, budget figures and assigned labels. An error occurs if the project is not found.
Action
Get taskReturns a single COR task by its id, including its title, project, deadline, status and priority.
Action
List clientsReturns all clients in the COR account, optionally narrowed by filter criteria.
Action
List feesReturns the fees in the COR account, including each fee's name, estimate, status and dates.
Action
List hoursReturns the time entries logged in the COR account, optionally narrowed by date range, client, project, user, label or team, and sorted as you choose.
Action
List productsReturns all products in the COR account, each with its name, client and brand.
Action
List projectsReturns the company's projects, optionally narrowed by client, team, user, brand, product, dates, status, health or archived state.
Action
List tasksReturns the tasks in your COR account, optionally narrowed by project, project manager, status and other criteria, and sorted the way you choose.
Action
List teamsReturns the teams in the COR workspace, including each team's name and description.
Action
Update ProjectUpdates an existing project in COR, changing only the fields you fill in, and returns the updated project.
Action
Update TaskUpdates an existing task by its id, changing its title, project, description, deadline, status, priority or archived state, and returns the updated task.
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 COR
ActiveCampaign to CORActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to COROrganize anything with Airtable, a modern database created for everyone.
Asana to CORAsana is a collaborative information manager for workspace.
ClickUp to CORClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to CORBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CORCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
Cliniko and COR, 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 COR when something happens in Cliniko?
Any of COR's 24 actions, including Create Client, Create Fee, Create Hour and Create Invoice. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from COR to Cliniko?
Yes. When something happens in COR, your agent can act in Cliniko too. This page covers both directions: COR's triggers and Cliniko's actions are listed here as well.
Do I have to build a connector for Cliniko or COR?
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 COR 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.