MILabs
Integrations

Appointment reminder automation for Cliniko

How an appointment reminder automation can read Cliniko bookings, send messages and log replies for staff review.

Updated 2026-10-12

Appointment reminder automation with Cliniko

Cliniko holds the diary, client details and notes for many allied health and dental clinics, and reminder messages are a steady source of repetitive work. An appointment reminder automation sits beside that system. It reads upcoming bookings, works out which reminder is due for each one, and drafts or sends the message through a channel the clinic approves. Replies such as confirm, reschedule or cancel can be routed back to the front desk so staff see the current state of each visit. The build suits clinics where phone calls to confirm sessions take up a regular part of the day. Because Cliniko remains the source of truth, the automation should write only what the clinic has agreed to, and every message should be logged. The first decisions are practical: which appointment types need reminders, what wording suits the clients, and who checks replies that do not match an existing booking.

How it works

  1. Confirm in the Cliniko account which API permissions the clinic can grant, then create a dedicated set of credentials for the reminder workflow.

  2. Map each appointment type to a reminder schedule, so the workflow knows which bookings need a message and when it should go out.

  3. Connect a workflow tool such as Zapier, Make or n8n to read upcoming appointments through the Cliniko API on a schedule the clinic sets.

  4. Send drafted messages by email or text using templates that name the clinic and its location, and log each message sent.

  5. Route replies to confirm, reschedule or cancel back to the matching appointment where permissions allow, and flag unmatched replies for staff.

  6. Test with sample records first, and copy approved text into Cliniko by hand until the reply path has been checked.

good questions, straight answers

Frequently asked questions

How does an appointment reminder automation hand work to a person in Cliniko?
A handoff happens when a reply does not fit a simple rule, such as a message that matches no booking. The workflow should flag that reply and place it in a queue the front desk checks. Staff then open the appointment in Cliniko, confirm the change, and record the outcome there. The automation should never make a clinical decision or alter treatment details. Naming an owner for each exception means nothing waits unseen.
Can an appointment reminder automation work with Cliniko data exports?
It can, although an export is a snapshot rather than a live view. A file of upcoming bookings can drive a reminder run, but it will be out of date once a client moves an appointment. For that reason the clinic should prefer reading live data through the Cliniko API where its permissions allow. Exports still help when testing message templates. Any file containing client names or contact details should be stored and deleted under the clinic's privacy rules.
What should I back up in Cliniko first?
Before any automation touches the diary, the clinic should export or otherwise secure the records it cannot afford to lose, including appointment history, client contact details and invoices. Record who holds the API credentials and where they are stored. A clear inventory of which fields the workflow will read and write also helps, because it shows what a change could affect.
How does an appointment reminder automation connect to Cliniko?
The usual route is the Cliniko API, which other software can call using credentials the clinic creates in its own account. A workflow tool such as Zapier, Make or n8n can run on a schedule, read upcoming appointments, and send the message. Where the permissions allow it, the same connection can write a reply status back to the booking. The clinic should confirm which read and write actions its account allows before the build starts.
Do I need a developer to connect an appointment reminder automation to Cliniko?
Often a developer or a technically confident staff member is useful, because the API connection, field mapping and error handling need careful setup. A no-code workflow tool can handle simple reminder rules without custom code, but the clinic still needs someone to own the credentials and review the logs. The scope of the work depends on how many appointment types exist and how replies are handled. A short written plan helps the person doing the setup know which checks come first.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.