Cliniko Custom Fields in Gohighlevel
Every Cliniko patient and appointment detail Universal Plugins writes into Gohighlevel custom fields, searchable and downloadable as CSV so you can use them in workflows and messages.
Custom fields are how appointment detail becomes usable inside Gohighlevel. Practitioner, service, appointment date and time, location, status and booking reference are written onto the contact, so a reminder, recall or review request can reference the real visit instead of generic wording.
Import them once before activating the webhook. The reference on this page lists every field the integration writes, grouped so you can search for the one you need, and can be downloaded for a bulk import rather than typed in one at a time.
Keep the field keys as supplied - workflows and message templates reference them by key, so renaming a field breaks the sequences that depend on it.
Why the fields matter
Custom fields are what turn a synced appointment into something a message can talk about. Practitioner, service, appointment date and time, location, status and booking reference are written onto the Gohighlevel contact, so a reminder can say who the patient is seeing, for what, when and where, and a recall can wait the right interval after the right service.
Without them the integration still connects records, but every message has to fall back on generic wording that patients notice and ignore.
Importing them
Import the full set once, before you activate the webhook, so the first synced appointment has somewhere to land. The reference on this page lists every field the integration writes, grouped and searchable, and can be downloaded so you can bulk import instead of creating fields one at a time.
Use the search box to jump to a specific field, or filter by group when you are checking a whole category such as appointment timing or practitioner detail.
Rules to follow
Keep the field keys exactly as supplied. Workflows and message templates reference fields by key, so renaming one breaks every sequence that reads it - and it fails quietly, with a message going out missing its detail rather than an obvious error.
If you need a friendlier label for internal use, change the display label and leave the key untouched.