Jane to GoHighLevel Custom Fields: What Clinic Data Can You Use?

ClinicSync Pro is an independent product that connects supported clinic systems, including Jane, with GoHighLevel. Data retrieved through the integration can be mapped to GoHighLevel contact custom fields, where it can be used for filtering, workflow conditions and personalised communications.

A video demonstration published in April 2025 showed approximately 86 Jane-related custom fields in one example configuration. That number should be treated as a point-in-time example rather than a guaranteed current field count. Available mappings can evolve, and the fields in a particular GoHighLevel account depend on its integration and configuration.

The basic process has three parts: Jane remains the source of the clinic data, ClinicSync Pro passes supported data into GoHighLevel, and GoHighLevel uses the mapped fields within contact records and workflows.

The demonstration grouped Jane data into several useful categories rather than limiting the integration to basic contact details.

Payment-related fields included available credit, amounts owing, claims amounts, loyalty balances, total payments and remaining balances. These values were described as coming from Jane rather than being recalculated inside the integration.

Patient activity fields included total appointments and counts for outcomes such as cancellations, no-shows, reschedules and arrivals. These fields can help clinics create operational segments based on appointment history.

Appointment fields covered upcoming, second upcoming and previous appointments. Examples included start times, location, treatment and appointment status information.

Other demonstrated fields included credit card expiry, referring professional details, referring staff member identifiers, patient profile notes, notification preferences and the date on which a record was last updated through the API.

Date-formatted custom fields can be useful when a workflow needs to run before or after a particular event. The video demonstrated this with a formatted credit card expiry field and appointment reminder start times.

For example, a clinic could configure a workflow to identify a populated card expiry field and send an appropriate reminder before the expiry date. If the clinic has an approved online process for updating payment details, the message could direct the patient to that process.

Upcoming appointment reminder fields can similarly provide the timing input for appointment-related workflows in GoHighLevel. Before activating a workflow, test the field format, time zone and behaviour when the field is empty.

Appointment totals and status counts make it possible to create more relevant contact segments. A clinic could identify patients with previous no-shows, distinguish active patients from those without an upcoming appointment, or build follow-up lists based on the most recent appointment.

These fields should be used as workflow inputs rather than assumptions about a patient. For example, a no-show count can place a contact into an internal review process, while the last appointment date can support a carefully designed reactivation campaign.

Upcoming and previous appointment details may also be inserted into supported messages or used as workflow conditions. Always account for missing or changing appointment data before allowing a workflow to send automatically.

The demonstrated integration included financial values sourced from the payment and balance information associated with a Jane patient profile. These fields could support internal lists or communications about an outstanding account.

Because the integration passes through values from the source system, clinics should investigate unexpected figures in Jane rather than assuming GoHighLevel calculated them. Insurance claims and other account activity may affect how Jane presents a balance.

Financial workflows should include safeguards for blank, zero, negative or recently changed values. Clinics should also review message wording and their own privacy, consent and data-handling requirements before using financial information in automated communications.

The video demonstrated notification-related fields taken from the patient profile in Jane. These may help a clinic incorporate recorded communication preferences into GoHighLevel workflow logic.

A field being available does not by itself determine whether a particular marketing or service message should be sent. Clinics remain responsible for configuring workflows appropriately and applying their own consent and communication policies.

A field labelled as the last updated date via API was demonstrated as a way to inspect data recency. In GoHighLevel, the field can be added as a contact-list column and used to sort records by the most recent integration update.

This can help an administrator find records that have not been updated recently, validate a new configuration or investigate whether a contact contains stale data. The video did not establish a universal update interval, so the timestamp should be used as an inspection tool rather than a promise of a particular sync frequency.

Start with a specific clinic process rather than activating automations for every available field. Useful starting points may include upcoming appointment reminders, card expiry notices, balance follow-up, no-show review or patient reactivation.

For each workflow, document the source field, expected format, trigger condition, handling of empty values, communication channel and exit condition. Test with non-production records before applying the workflow to a wider patient list.

Custom-field mapping should not be interpreted as automatically mirroring the Jane calendar into GoHighLevel. This article covers the use of supported Jane data in GoHighLevel custom fields and workflows.