Cliniko Webhook Triggers for Gohighlevel
Fire Gohighlevel workflows from Cliniko events in real time: patient created or updated, appointment booked, rescheduled, cancelled or marked as a no-show, and invoice created or paid.
Triggers start a Gohighlevel workflow the moment something happens in Cliniko. A new booking, a reschedule, a cancellation, a no-show or a completed appointment can each launch its own sequence, so follow-up begins while the visit is still fresh in the patient's mind.
Because the trigger fires from the practice management system rather than from a form, the automation reflects what actually happened in the clinic - including bookings taken over the phone or at reception. That is what makes reminder, recall and no-show recovery sequences reliable rather than approximate.
Pair triggers with the appointment custom fields so every message can reference the practitioner, service, date, time and location without manual entry, and branch on appointment type when different services need different follow-up.
Why diary triggers beat form triggers
A form tells you what someone asked for. A trigger from the Cliniko diary tells you what the clinic actually committed to, including bookings taken at reception or over the phone that never touched a web form. That difference is what makes reminder, recall and no-show recovery sequences trustworthy enough to leave running unattended.
Triggers fire in near real time, so a sequence starts while the visit is still fresh: a confirmation the moment a booking is made, a recovery message the same afternoon as a no-show, a review request the evening a course of treatment finishes.
Building on top of a trigger
Pair each trigger with the appointment custom fields so the message can name the practitioner, service, date, time and location without anyone typing them. Branch on appointment type when different services need different follow-up - an initial consultation, a review and a treatment block rarely deserve the same wording.
Add a wait step rather than sending immediately where it makes sense; a cancellation recovery message often works better an hour later than in the same minute the slot is released.
Keeping sequences accurate
Because reschedules and cancellations arrive as their own events, sequences can correct themselves: a moved appointment updates the reminder rather than sending one about a time that no longer exists, and a cancellation ends the sequence instead of continuing it.
Keep field keys exactly as supplied. Workflows and message templates reference them by key, so renaming a field silently breaks every sequence that reads it.