Integration
Can Cliniko connect to Zapier or Make?
Zapier does not have a Cliniko app; its directory returns nothing for Cliniko. Make lists a Cliniko connector, but it is built and maintained by a community developer, not Make or Cliniko, with triggers for new or ended appointments and new patients, and actions to create or archive contacts and patients. Either route sends patient data to a third party outside Cliniko.
Last checked 25 Sep 2026 against the sources listed at the end of this page.
What syncs, and when
| What | Direction | When | Notes |
|---|---|---|---|
| Zapier | No connection available | n/a | Cliniko does not appear as an app in Zapier's own directory. A Cliniko automation built through Zapier has to go through a general purpose connector platform instead of a dedicated Zapier app. |
| New or ended appointment | Cliniko to Make | Appointment created or marked ended in Cliniko | Make's community built Cliniko app lists watching for new appointments and ended appointments among its available triggers. |
| New patient | Cliniko to Make | Patient added in Cliniko | Listed as a trigger on Make's Cliniko app, alongside the appointment triggers. |
| Contact and patient records | Make to Cliniko | Zap or scenario runs an action | Make's Cliniko app lists actions to create a new contact, archive a contact, and archive a patient, run against the Cliniko API using an API key. |
What does not sync
- A polling interval or delay figure for the Make Cliniko app. Make's own listing for the app does not state how often it checks Cliniko for new triggers, so a practice relying on it for anything time sensitive should test the actual delay rather than assume it is instant.
- Any official support from Cliniko or Make. Make's own page describes the Cliniko app as developed, supported and maintained by community users, not by Make itself, so a broken trigger is a community developer's problem to fix, not a support ticket to Cliniko or Make.
- Data staying within Cliniko's own systems. Both routes require an API key that hands patient data, such as names, appointment details and contact records, to a platform outside Cliniko's own infrastructure.
Zapier does not have a Cliniko app at all
This is worth stating plainly because Zapier is the automation platform most people mean when they ask about connecting Cliniko to something else. Cliniko does not appear in Zapier's own app directory, and searching for it returns nothing. Anyone offering a "Zapier to Cliniko" automation is routing it through a general connector platform that then talks to Zapier, not a dedicated Cliniko app inside Zapier itself.
Make is different: it lists an actual Cliniko app, with triggers for new patients and new or ended appointments, and actions to create or archive a contact or patient. But Make's own listing describes this app as community built, maintained by an outside developer rather than by Make or Cliniko, and used in a modest number of scenarios by Make's own count.
What that means day to day
A community built connector still works through Cliniko's own API, using an API key the practice generates the same way it would for Xero or Mailchimp. What it does not come with is the assurance that Cliniko's own integrations carry: if the connector breaks after a Cliniko update, the fix depends on the community developer maintaining it, not on Cliniko's support team.
Make's page for the app does not spell out how often its triggers check Cliniko for new appointments or patients. Automation platforms built this way are typically polling based rather than instant, checking every few minutes rather than reacting the moment something changes in Cliniko, but without a stated figure a clinic should test the actual delay against its own use case before building a workflow that assumes it is immediate.
The part worth pausing on before building anything
Every trigger and action here moves identifiable patient information, names, appointment times, contact details, out of Cliniko and into a third party automation platform. Under Australian Privacy Principle 11, a practice holding that information has to take reasonable steps to protect it, and under Australian Privacy Principle 8, sending it to a service that may process or store data overseas is itself a disclosure the practice needs to have a lawful basis and safeguards for.
None of that is a reason to rule automation out. It is a reason to know what data a given Zap or Make scenario actually touches before switching it on, and to prefer whichever connector's provider can tell you plainly where the data goes and how long it is kept.
Sources
- Cliniko does not appear as an app in Zapier's directory; searches for a Cliniko integration on Zapier's own site return no dedicated app page. Zapier, checked 25 Sep 2026.
- Make lists a Cliniko app described as developed, supported and maintained by community users rather than by Make itself, with triggers including new appointment, ended appointment and new patient, and actions to create or archive a contact or patient, run through a Cliniko API key. Make, checked 25 Sep 2026.
- Under Australian Privacy Principle 11, an organisation holding personal information must take steps that are reasonable in the circumstances to protect it from misuse, interference, loss, and unauthorised access. Office of the Australian Information Commissioner, checked 25 Sep 2026.
- Under Australian Privacy Principle 8, disclosing personal information to an overseas recipient, including via a cloud service used to store or process it, carries separate obligations from domestic use, and organisations need a risk based approach to how that information is handled once it leaves Australia. Office of the Australian Information Commissioner, checked 25 Sep 2026.