Resources · Make integration

Cliniko Make integrationAutomate Cliniko with Make.

Patients, appointments, invoices and stock can move out of Cliniko on their own. The Cliniko Make integration gives you 38 modules: 6 triggers, 24 actions and 8 searches. This guide helps clinic managers connect the account, build a first scenario and pick the right module.

Try the Cliniko integration on MakeSee the 38 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cliniko Make integration automate?

The Cliniko Make integration links your clinic account to Make, a visual tool where you chain apps without code. The automation you build is called a scenario. Each brick in it is a module, and Cliniko brings 38 of them: 6 that watch for new records, 24 that act, 8 that search.

A cleaner accounting export. For a practice that issues plenty of invoices, Watch New Invoices picks up each invoice, Search Invoice Items reads the lines, and a spreadsheet module in another app stores them. The Airtable Make integration is a common destination.

Patients created from outside forms. A booking request lands in another tool; Create a Patient opens the file in Cliniko and Create an Individual Appointment books the slot, with no retyping at the front desk.

Stock that follows sales. When a product sale is recorded elsewhere, Create a Product Stock Adjustment lowers the quantity in Cliniko so the shelf and the software agree.

Know the limits before you start. All six Cliniko triggers are scheduled: Make checks the account at intervals, nothing reaches Make the second a record changes. The list has no delete module either, only archive and cancel. For anything outside the list, Make an API Call reaches the Cliniko API with the same connection.

Hesitating between tools? The n8n vs Make comparison lays out the criteria, and Make training covers the editor from scratch.

Connect

How do you connect Cliniko to Make?

  1. 01

    Create an API key in Cliniko

    In Cliniko, click My Info at the bottom left of the navigation to reach your user profile. Press Manage API keys, create a key if none exists yet, and copy the one shown on screen.

  2. 02

    Add a Cliniko module in Make

    Open your scenario in Make, add any Cliniko module and click Create a connection. A connection is your Cliniko account linked to Make once, then reused by every Cliniko module you add.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like (this field is optional), paste the API key you copied, and follow the on-screen instructions to finish.

First scenario

Your first scenario with Cliniko

GoalWhen a booking request arrives from another app, Make creates the patient in Cliniko and books an individual appointment.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the app where requests arrive, such as your form tool.

  2. 02

    Add Create a Patient

    Click the + on the right of that module, search for Cliniko, pick Create a Patient and click Create a connection to link your account with the API key.

  3. 03

    Map the patient details

    Fill the module by mapping data from the form: each answer that came in is a bundle, one item passed from module to module, and you drop its values into the Cliniko fields.

  4. 04

    Book the appointment

    Add Create an Individual Appointment with the next +. Map the patient Make just created and the slot details from the form, so the booking lands on the right file.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received, then check that the new patient and appointment appear in Cliniko.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (a new scenario runs every 15 minutes by default) and switch the scenario on. Every module run counts as one operation on your Make plan.

Triggers

What starts a Cliniko scenario

6 modules start a scenario when something happens in Cliniko. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Cliniko as soon as it happens.

Cliniko1Watch Ended Appointments

Watch Ended Appointments

Scheduled trigger

In Make“Watches for ended appointments.”

Picks up appointments once they are over, so the after-visit work starts without anyone remembering it. Each finished appointment comes out as its own bundle for the modules that follow.

How it fires
scheduled. Make checks Cliniko on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
sending a feedback request or a follow-up note after a consultation, through another app.
Watch out
the follow-up leaves at the next check, not the minute the patient walks out; say so in any message that promises speed.
Cliniko2Watch New Appointments

Watch New Appointments

Scheduled trigger

In Make“Watches for new appointments.”

Hands you every appointment newly booked in Cliniko, ready to copy into a calendar, a team chat or a reporting sheet.

How it fires
scheduled. Make polls Cliniko at the interval set on the scenario, never faster than 15 minutes on the Free plan.
When to use it
alerting a practitioner's assistant about fresh bookings, or keeping a shared planning view up to date.
Watch out
it is built for new bookings; when a later step needs the current state of a booking, fetch it again with Get an Individual Appointment.
Cliniko3Watch New Contacts

Watch New Contacts

Scheduled trigger

In Make“Watches for new contacts.”

Brings each contact added in Cliniko into your scenario, which keeps a second address book or a mailing list in step with the clinic without exports.

How it fires
scheduled. On every scheduled run, Make asks Cliniko for contacts it has not seen yet.
When to use it
copying new referrers or partner contacts into a CRM after the front desk records them in Cliniko.
Watch out
Make lists patients and contacts as separate modules for Cliniko; to follow new patient files, Watch New Patients is the trigger to pick.
Cliniko4Watch New Invoices

Watch New Invoices

Scheduled trigger

In Make“Watches for new invoices.”

Delivers every newly issued invoice to your scenario, which is the starting point for bookkeeping exports and revenue dashboards built outside Cliniko.

How it fires
scheduled. Make checks for new invoices each time the scenario's schedule comes round.
When to use it
filling an accounting sheet line by line, or warning the finance lead about each invoice issued.
Watch out
the trigger gives the invoice, not necessarily its detailed lines; add Search Invoice Items after it when you need the billed products or services one by one.
Cliniko5Watch New Patients

Watch New Patients

Scheduled trigger

In Make“Watches for new patients.”

Catches each patient file created in Cliniko, so a welcome message, an intake form or a CRM entry can follow without a manual step.

How it fires
scheduled. Make looks for new patients whenever the scenario runs, on the interval chosen in Scheduling.
When to use it
welcoming first-time patients through your email tool, or adding them to a newsletter list with their consent.
Watch out
only new files trigger it; changes made later to an existing patient go unnoticed, and there is no Watch Updated Patients in the list.
Cliniko6Watch Updated Contacts

Watch Updated Contacts

Scheduled trigger

In Make“Watches for updated contacts.”

Surfaces contacts whose details changed in Cliniko, which lets a copy elsewhere stay correct after a new phone number or address is saved.

How it fires
scheduled. Make compares on each scheduled run and passes along the contacts edited since the last check.
When to use it
carrying each correction made in Cliniko over to a referrer directory kept in another app, at Make's next check.
Watch out
if the next module writes the change back to Cliniko with Update a Contact, the edit is seen again on the following run; keep the destination outside Cliniko.
Modules

Everything the Cliniko modules can do

Cliniko gives you 32 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Cliniko1

Archive a Contact

Action

In Make“Archives a single contact.”

Takes a contact out of the active list in Cliniko while keeping the record, which tidies the address book without losing history.

When to use it
a referrer closes their practice and the team should stop seeing them in searches.
Watch out
the list offers no unarchive module for contacts, only for patients, so restoring one means doing it in Cliniko.
Cliniko2

Archive an Individual Appointment

Action

In Make“Archives a single individual appointment.”

Removes a single appointment from the active diary by archiving it, useful when a booking should disappear from view rather than show as cancelled.

When to use it
clearing duplicate bookings that an outside form created twice for the same slot.
Watch out
for a visit the patient called off, Cancel an Individual Appointment says what actually happened; pick the module that matches the reason.
Cliniko3

Archive a Patient

Action

In Make“Archives a single patient.”

Moves a patient file to the archive in one step, so inactive people stop cluttering searches while their record stays in Cliniko.

When to use it
a patient asks to leave the clinic list and you handle the request from a form in another app.
Watch out
archiving is reversible here, since Unarchive a Patient exists in the same app; test with Run once on a dummy file first.
Cliniko4

Archive a Product

Action

In Make“Archives a single product.”

Retires a product from the active catalog in Cliniko, which keeps sales screens short once an item is discontinued.

When to use it
your supplier sheet marks a brace or a cream as no longer available and Cliniko should follow.
Watch out
there is no unarchive module for products in the list; bringing an item back is done by hand in Cliniko or through Make an API Call.
Cliniko5

Cancel an Individual Appointment

Action

In Make“Cancels an individual appointment by its id.”

Marks one appointment as cancelled, which frees the practitioner's slot and keeps an honest trace of the no-go.

When to use it
a patient replies to a reminder from another tool that they cannot come, and the booking should update without a phone call.
Watch out
the module works from the appointment id, so place Search Individual Appointments or a trigger before it to supply that id.
Cliniko6

Create a Contact

Action

In Make“Creates a new contact.”

Adds a new contact to Cliniko from data coming out of another app, sparing the front desk a round of copy and paste.

When to use it
a GP or insurer fills your partner form and should appear in Cliniko's contacts straight away.
Watch out
run Search Contacts first if the same person may already exist, otherwise each form reply creates one more duplicate.
Cliniko7

Create an Individual Appointment

Action

In Make“Creates a new individual appointment.”

Books a one-to-one appointment in Cliniko from your scenario, so requests collected elsewhere end up in the practitioner's diary.

When to use it
an online request form or a chat assistant gathers the slot and the patient, and the booking should exist without retyping.
Watch out
map records that already exist in Cliniko; Search Patients and Search Practitioners find them so you can drop them into the booking.
Cliniko8

Create a Patient

Action

In Make“Creates a new patient.”

Opens a new patient file in Cliniko with the details your scenario maps in, the first brick of any intake flow.

When to use it
a new-patient questionnaire filled on your website should produce the file before the first visit.
Watch out
place Search Patients before it and continue only when nothing is found, or a returning patient ends up with two files.
Cliniko9

Create a Product

Action

In Make“Creates a new product.”

Adds an item to the Cliniko product list from another source, handy when your catalog lives in a supplier sheet or an online shop.

When to use it
the purchasing lead adds a new supplement to the shared spreadsheet and the clinic should be able to sell it.
Watch out
Search Products first avoids a second copy of an item that already exists under the same name.
Cliniko10

Create a Product Stock Adjustment

Action

In Make“Creates a new product stock adjustment. Increases or decreases product stock quantity”

Raises or lowers the stock quantity of a product in Cliniko, keeping the count right when goods move outside the software.

When to use it
a delivery is logged in the purchasing tool, or a sale happens in an online shop, and Cliniko's stock should match.
Watch out
the adjustment adds to or subtracts from the current figure; running the same scenario twice on one delivery counts it twice.
Cliniko11

Get a Booking

Action

In Make“Retrieves an existing booking by its id.”

Reads one booking in full from its id, giving the next modules all the details of that slot to work with.

When to use it
another app sends you a booking reference and you need the rest of the information before writing a message.
Watch out
without an id this module has nothing to fetch; when you only know a patient or a date, Search Bookings is the right start.
Cliniko12

Get a Contact

Action

In Make“Retrieves a single contact by ID.”

Returns a single Cliniko contact from its ID, so a scenario can enrich a message or a record with the full details.

When to use it
a trigger gave you a contact reference and the email you are about to send needs the name and address.
Watch out
map the ID from a previous module rather than typing it, then test with Run once and read the bundle before switching on.
Cliniko13

Get an Individual Appointment

Action

In Make“Retrieves an existing individual appointment.”

Fetches the current state of one appointment, which is the safe way to act on the latest version rather than on older data.

When to use it
just before sending a reminder, to make sure the appointment still stands as booked.
Watch out
it reads one appointment you already identify; to look across a period or a practitioner, go through Search Individual Appointments.
Cliniko14

Get an Invoice

Action

In Make“Retrieves a single invoice by id.”

Loads one invoice from its id so its amounts and status can feed an export, a reminder or a dashboard.

When to use it
your accounting tool reports a payment and you want to check the matching Cliniko invoice before marking anything.
Watch out
the invoice lines are separate records; add Search Invoice Items when the detail per product or service matters.
Cliniko15

Get an Invoice Item

Action

In Make“Retrieves a single invoice item by id.”

Pulls a single line of an invoice by its id, handy when a report tracks what was billed rather than the invoice total.

When to use it
checking one billed service that another system flagged, such as a disputed treatment line.
Watch out
you need the item id; most flows reach it through Search Invoice Items first, then use this module only for a precise lookup.
Cliniko16

Get a Patient

Action

In Make“Retrieves an existing patient by given ID.”

Retrieves a patient file from its ID, giving later modules the patient's full details for a message, a sheet or another app.

When to use it
after Watch New Invoices, to add the patient's name to each line of the accounting export.
Watch out
it needs an exact ID; if you start from a name or an email, run Search Patients instead.
Cliniko17

Get a Practitioner

Action

In Make“Retrieves an single practitioner by its id.”

Reads one practitioner's profile from its id, useful to put a name on an appointment or route work to the right person.

When to use it
a new booking comes through and the notification should tell the assistant which practitioner it belongs to.
Watch out
each call costs one operation; in a busy flow, avoid calling it for every bundle when the same practitioner repeats.
Cliniko18

Get a Product

Action

In Make“Retrieves a single product by id.”

Loads a single product from its id, so a scenario can read the current details before adjusting stock or updating a shop.

When to use it
before Create a Product Stock Adjustment, to log the item's name in a purchasing sheet next to the movement.
Watch out
with only a product name to go on, Search Products is the entry point, not this module.
Cliniko19

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Cliniko API to your scenario, reusing the connection you already created, for anything the ready-made modules leave out.

When to use it
you need a record type or an action absent from this page, and that the Cliniko API documentation describes.
Watch out
you write the request yourself, so keep the Cliniko API documentation open and test every call with Run once.
Cliniko20

Unarchive a Patient

Action

In Make“Unarchives a patient.”

Brings an archived patient file back to the active list, which undoes an archive made by hand or by another scenario.

When to use it
a former patient books again through your website form and the old file should reappear instead of a new one.
Watch out
despite its internal key mentioning contacts, Make labels this module for patients; archived contacts are not restored here.
Cliniko21

Update a Contact

Action

In Make“Updates an existing contact.”

Changes the details of an existing contact in Cliniko, so the address book reflects corrections made in another tool.

When to use it
your CRM is the reference for partner details and Cliniko should follow each correction.
Watch out
do not start this flow from Watch Updated Contacts on the same account, or each update triggers the next run in a loop.
Cliniko22

Update an Individual Appointment

Action

In Make“Updates an existing individual appointment.”

Edits a booked appointment in place, keeping the diary right when details change after the booking.

When to use it
a patient moves their visit through a self-service page in another app and Cliniko should show the new slot.
Watch out
identify the appointment first with Search Individual Appointments or Get an Individual Appointment, then map only the values that change.
Cliniko23

Update a Patient

Action

In Make“Updates an exisitng patient.”

Writes new information into an existing patient file, which saves the reception team from copying changes by hand.

When to use it
patients update their phone or address in an online form and the Cliniko file should follow.
Watch out
an empty mapped value can overwrite good data; check in Run once which fields your form really sends.
Cliniko24

Update a Product

Action

In Make“Updates an existing product.”

Adjusts a product's details in Cliniko from your scenario, so names and descriptions stay the same across tools.

When to use it
the supplier spreadsheet changes a product's description and the clinic catalog should match.
Watch out
quantities move through Create a Product Stock Adjustment, not here; keep this module for the product sheet itself.
Cliniko25

Search Bookings

Search

In Make“Searches for bookings.”

Finds the bookings that match your criteria and returns them one by one, the way to work on a set of slots at once.

When to use it
building a list of upcoming visits to share with the team in another app.
Watch out
a search can return zero, one or many bundles; every following module runs once per result and uses operations accordingly.
Cliniko26

Search Contacts

Search

In Make“Searches for contacts.”

Looks through Cliniko contacts and returns the matches, which is how a scenario checks whether someone is already on file.

When to use it
before Create a Contact, so a partner who fills your form twice is not added twice.
Watch out
when nothing matches, the modules after it receive no bundle and do not run; plan for that case during the Run once test.
Cliniko27

Search Individual Appointments

Search

In Make“Searches for individual appointments.”

Lists the individual appointments that fit your filters, giving the scenario each one as a separate bundle to process.

When to use it
collecting a practitioner's upcoming visits to send reminders through a messaging app.
Watch out
a broad search returns many results, each one costing operations in the modules downstream; narrow the criteria before switching on.
Cliniko28

Search Invoice Items

Search

In Make“Searches for invoice items.”

Returns the lines behind your invoices, the detail needed when accounting or reporting follows services and products rather than totals.

When to use it
right after Watch New Invoices, to write each billed line into a revenue sheet.
Watch out
an invoice with several lines produces several bundles, so the next module runs once per line, not once per invoice.
Cliniko29

Search Invoices

Search

In Make“Searches for invoices.”

Pulls the invoices that match your criteria, a good base for catching up past billing that no trigger ever picked up.

When to use it
exporting existing invoices to a new accounting sheet when the scenario is first set up.
Watch out
for new invoices from now on, Watch New Invoices is the lighter choice; a search reruns over the same records each time.
Cliniko30

Search Patients

Search

In Make“Searches for patients by different criteria.”

Finds patients by different criteria and sends back each match, the usual check before creating or updating a file.

When to use it
a form reply arrives with a name and an email, and the scenario must know whether that person is already a patient.
Watch out
two patients can share a name; prefer a more precise criterion when your form collects one.
Cliniko31

Search Practitioners

Search

In Make“Searches for practitioners.”

Returns the clinic's practitioners that fit your search, so a scenario can pick the right person before booking or notifying.

When to use it
an outside booking form names a practitioner and Create an Individual Appointment needs that practitioner's record.
Watch out
the list rarely changes, so keep this search out of loops that repeat it for every bundle.
Cliniko32

Search Products

Search

In Make“Searches for products.”

Scans the Cliniko product list and returns what matches, the link between an item name from another tool and its record in the clinic.

When to use it
an online order names a product and you need its record before Create a Product Stock Adjustment.
Watch out
slight spelling differences between tools can return nothing; align product names on both sides first.
Need help

Need help automating Cliniko with Make?

A person reads every message.

FAQ

Cliniko and Make: common questions

01Is the Cliniko Make integration free?
Yes, on the Make side. Cliniko is a standard app, available from the Free plan like the 3,000+ other standard apps. The Free plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes and caps files at 5 MB and transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) bring a 1 minute interval, unlimited active scenarios and 40 minute runs. Usage counts in operations. You still need an active Cliniko subscription.
02What do you need to connect Cliniko to Make?
An active Cliniko account and an API key. In Cliniko, open your user profile from the link at the bottom left of the navigation, click Manage API keys, create a key if none exists and copy the key displayed on screen. In Make, add a Cliniko module, click Create a connection, optionally name it, then paste the key. The same connection serves all 38 Cliniko modules, so this setup happens once per account.
03Do Cliniko triggers in Make fire in real time?
No. All 6 Cliniko triggers are scheduled: Make checks Cliniko on the scenario's schedule and processes what changed since the last check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. There is no instant trigger for Cliniko in Make, so plan any patient message with that delay in mind, and avoid promising an immediate reply.
04What if a Cliniko module is missing in Make?
Use Make an API Call. Cliniko has this module, which calls any endpoint of the Cliniko API with the connection you already set up. It covers what the 24 actions and 8 searches do not, such as a record type absent from the list or an action with no ready-made module. You build the request yourself, so keep the Cliniko API reference nearby and check the result with Run once.
05Should you use Make or n8n for Cliniko?
It depends on your team. Make gives Cliniko 38 ready-made modules covering patients, contacts, appointments, invoices, products and practitioners, set up in a visual editor with guided connections. n8n is another automation tool, and the choice often follows the one your team already runs. Check whether a ready-made Cliniko node exists there for your use case, then compare both tools on the criteria that matter to you, as laid out in the n8n vs Make comparison on this site.
Same platform

Other docs you might need on this stack.

Browse all integrations