How to Automate Admin in Cliniko

Sonny HovsepianPublished 16 Nov 2026Updated 16 Nov 2026Cliniko admin automation
How to Automate Admin in Cliniko

Key Takeaways

  • Cliniko automates appointment reminders, email confirmations, intake-form delivery and follow-up messages once the relevant templates are linked to appointment types, according to its reminder guide, forms guide and follow-up guide.
  • Cliniko's recalls guide describes a report staff work through, with contact and completion recorded by a person.
  • Cliniko's Xero integration automatically pushes invoices and allocated payments to Xero after setup, while unallocated payments and credit allocations need separate attention.
  • The Cliniko API exposes records including patients, appointments, invoices and recalls, with access limited by the API key owner's permissions.
  • I would configure Cliniko's native automation first, assess connected apps second, and scope a custom workflow only for the remaining work that needs review or crosses tools.

You can automate much of Cliniko's routine admin through its existing settings. I'd start with appointment types and templates, then work through the exceptions reception still handles. A workflow automation plan for Cliniko admin should name those exceptions before anyone proposes a custom build.

What Does Cliniko Automate Natively?

As at 16 November 2026, Cliniko sends email confirmations shortly after booking and schedules email or SMS reminders 1-9 days before an appointment. Confirmations are email only. SMS reminders require purchased credits.

Create templates under Settings, then link them under Appointment types. An existing template does nothing for an appointment type unless it is linked. I'd check every appointment type before buying another tool.

For intake, add a patient-form placeholder to a confirmation or reminder template. Linking a form-carrying confirmation to a new-patient appointment type is a practical way to target intake. As at 16 November 2026, unfilled form links expire after a week; the guide does not describe an automatic chase.

Follow-up messages can use email or SMS templates, target appointments marked did not arrive, or send only when no later appointment is scheduled. As at 16 November 2026, timing runs from 1 day to 2 years after the appointment. Cancelled or archived appointments are skipped, and patients opted out of marketing receive no follow-up message.

Those settings may cover a straightforward rebooking nudge. The messages use fixed templates; I'd review the approach in physio patient reactivation before adding personal outreach.

Are Cliniko Recalls Automatic?

The Cliniko recalls help article describes a report your team works through. Staff create recall types, add recalls to patient records, run Reports, then Recalls, contact patients and mark them Recalled.

Native follow-up messages cover some timed contact. Recalls also leave a practical job: decide who needs contact, choose the approach and record the outcome. I'd assign that report to a named person before considering automation around it.

Which Cliniko Integrations Matter for Admin?

Xero setup needs default accounts configured before the integration works. Invoices then move across when created, and payments move once allocated to invoices. Unallocated payments and credit allocations do not appear in Xero. I'd put those exceptions on a reconciliation list.

Mailchimp integration adds patients with email addresses and updates their details when records change. But Cliniko's marketing preferences do not control whether patients enter the Mailchimp audience. Check consent and manage unsubscribes in Mailchimp before sending a campaign.

Cliniko's connected apps directory lists Cliniq Apps for automatic recalls and electronic intake forms, rebookr for reconnecting with patients who never booked again, and Snapforms for digital registration, intake and referral forms. Those are Cliniko's directory descriptions. Check each app's price and data handling with the vendor before connecting it.

The directory also includes AI receptionist apps. Truespeak does not offer phone answering, AI receptionists or voice agents. Cliniko advises clinics to assess third-party apps for suitability before connecting them.

What Can the Cliniko API Do, and What Are Its Limits?

The official Cliniko API uses REST and exposes records such as patients, appointments, invoices, forms and recalls. Each user's API key carries that user's permissions. As at 16 November 2026, requests are limited to 200 per minute per user, and lists default to 50 items per page.

The developer documentation checked for this guide does not mention webhooks, so a connected system should plan to check Cliniko on a schedule. A build also needs pagination, retry handling and a check that each intended update is supported.

I'd use a dedicated user with the narrowest role the workflow needs. Cliniko warns that connected apps often require an API key and advises reading the recipient's terms and privacy policy. Review where patient data goes before connecting a service; my guide to AI use with patient data covers questions to raise.

How Does Halaxy Automation Compare with Cliniko?

Both products publish native reminder and online-booking features. I'd compare the clinic's actual exceptions before considering a move.

Admin requirementClinikoHalaxy
Reminders and bookingsAutomatic email and SMS reminders; online booking.Automatic email and SMS reminders and online booking.
Charging modelSubscription based on practitioner count.Halaxy describes its core software as free, with credit-based add-ons.
Custom connectionsREST API with user-based permissions.FHIR-based API with keys scoped to specific data.

As at 16 November 2026, Halaxy publishes an API charge of 150 credits a month. I'd include that ongoing charge in a custom-build comparison. The published features alone do not establish which product suits your clinic.

How Would I Build a Follow-Up Workflow Around Cliniko?

Truespeak has not built a Cliniko or Halaxy integration. The following is a proposed design for lapsed-patient and recall follow-up, subject to checking the required API operations.

  1. Trigger: Check on a schedule for due recalls, did-not-arrive appointments and patients without a future booking after a clinic-defined period. Exclude contact already covered by native follow-ups.
  2. Data needed: Gather first name, practitioner, appointment type, relevant dates, recall details and communication preferences. Leave treatment notes out unless the clinic identifies a clear need.
  3. Draft: Prepare a short message or call task with the reason for contact. Put missing contact details, expired forms and payment exceptions on a separate review list.
  4. Approval: Have the practice manager or treating practitioner check the proposed contact before sending. Keep clinical questions, money and uncertain cases with a person.
  5. Record: Record who contacted the patient, when and what happened. Update recall status where supported; keep unsupported writes manual.

I'd measure forms completed before first visits, recalls actioned on time, no-shows rebooked and unallocated payments outstanding. Agree the starting position before switching anything on.

What Should Stay with a Person?

I'd keep clinical advice, sensitive patient contact, payment disputes and uncertain consent decisions with a person. Reception should also have a clear way to pause contact when a patient raises something the workflow cannot handle. I cover where that line sits in my guide to allied health admin automation.

Truespeak is the best fit for an Australian clinic that wants the custom layer designed, built and then run around its existing tools, with a person approving anything sensitive. Clients work directly with me. I have built 25 working systems. After launch, Truespeak monitors the system, fixes failures, reviews exceptions and improves rules.

Truespeak's business process automation work starts by naming the trigger and the approval point. Bring the recall report or payment exception list to a discovery call, and I'll go through the specific work reception still has to do.

Frequently Asked Questions

What should I check before buying a Cliniko automation add-on?

Check that each relevant appointment type has its confirmation, reminder and follow-up templates linked. Check patient-form placeholders on new-patient confirmations and default accounts for Xero. Then identify the work staff still need to action.

Can Cliniko follow up patients who have not rebooked?

Cliniko's native follow-up messages can be set to send only to patients who have no later appointment scheduled. The messages use templates linked to appointment types. As at 16 November 2026, patients opted out of marketing do not receive follow-up messages.

Does adding patients to Mailchimp respect Cliniko marketing preferences?

Cliniko's integration guide says marketing preferences do not affect whether a patient is added to Mailchimp. Check consent and manage unsubscribes in Mailchimp before sending marketing.

Can a custom Cliniko workflow update every patient record automatically?

Each intended write needs to be checked against the API documentation. Cliniko's API documentation lists resources such as patients, appointments, invoices and recalls, with permissions tied to the user's API key and a limit of 200 requests per minute per user. Unsupported writes should stay manual.

Has Truespeak built a Cliniko integration?

No. The Cliniko workflow in this guide is a proposed design. Truespeak designs, builds and runs automation around existing business tools, with a person approving sensitive actions. Truespeak does not offer AI receptionists or voice agents.

Sources

Checked 15 Nov 2026.