Cliniko Gohighlevel Integration: How Two-Way Sync Works
The Cliniko Gohighlevel integration keeps patients and appointments in step in both systems, in real time and in both directions, with no middleware and no custom code.
- New Cliniko patients appear as Gohighlevel contacts with details in custom fields
- Appointments booked in Cliniko land on the mapped Gohighlevel calendar
- Bookings made in Gohighlevel are created in Cliniko
- Reschedules update instead of duplicating; cancellations and no-shows sync directly
- Cliniko businesses, practitioners and appointment types map to Gohighlevel calendars
Setup: install Universal Plugins in your Gohighlevel sub-account, add your Cliniko API key, map calendars, connect the webhook and activate the sync. MCP can be enabled on the same account so a Gohighlevel Voice AI agent can book during a live call.
What connecting Cliniko actually changes
The practical change is that nobody maintains two versions of the day. A booking taken at reception, a time moved by phone, a cancellation or a no-show marked after the fact each reach Gohighlevel within seconds, updating the contact, the appointment and the appointment fields your messages read from.
Bookings travel the other way too - from a Gohighlevel calendar, a form, or a Voice AI agent into Cliniko against the right business, practitioner and appointment type - so the practitioner diary stays the single source of truth.
Setup is configuration
Generate a secure Universal Plugins key from your Cliniko API key so the raw key is never stored, map businesses and practitioners to Gohighlevel calendars, import the custom fields, save the webhook in Cliniko, then run a test booking and confirm it appears in Gohighlevel with practitioner, service, date and time populated.
Only the mapping needs real thought, because it decides how location-specific wording and per-practitioner reporting behave later. Everything else is copying a value between two screens.
What to automate first
Reminders, then no-show and late cancellation recovery, then treatment plan recalls, then review requests. Each attaches to something the clinic already does every week, so the effect on the diary is visible within a month rather than a quarter.
Because every message reads its detail from the synced fields, one workflow covers many services and locations without separate copies to maintain.