ClinicSync Pro Documentation

Quick Reference: Field Sync Map

For a complete list of fields, and what gets synced between your EMR and GoHighLevel, check out our real-time mapping sheet.

How Syncing Works

ClinicSync Pro keeps your clinic data flowing automatically between Jane, Cliniko, Nookal, PtEverywhere, and GoHighLevel — with robust automations for booking, reminders, reactivation, and reporting.

Key Features:

Near real-time syncing every 5–30 minutes (contacts, appointments, invoices, purchases)
100% hands-off once connected — no manual exports or spreadsheet uploads needed
Secure, compliant, and isolated: HIPAA, GDPR, PIPEDA aligned

What Gets Synced?

Contacts: All patients/clients, including name, phone, email, DOB, and much more
Appointments: Past/future bookings, cancellations, no-shows, practitioner, room, and notes
Invoices/Payments: Revenue, payment source, outstanding balances
Purchases: Packages, products
Custom Fields: Enriched GHL contacts with total visits, last/next appt, status, retention, ROI fields

Supported Automations

AI Booking: Book appointments directly from SMS, email, or your website—with real-time EMR sync to prevent double-bookings.
No-Show & Reactivation: Automated reminders, win-back, and reactivation campaigns triggered by actual EMR data.
Review Requests: Automatically prompt for Google reviews after each attended visit.
KPI & ROI Dashboards: Live Looker Studio dashboards for patients, revenue, retention, and full ad ROI (Meta, Google, GHL calls).
Voice AI Booking: Enable seamless booking by phone through AI agents using your live GHL + EMR calendar sync.

These are just a few examples—the sky is truly the limit. If you can imagine it, you can automate it with ClinicSync Pro.

Walkthrough Videos & Tutorials

KPI & ROI Dashboard Walkthrough

See real dashboards for Jane, Cliniko, and PT Everywhere — track real-time ROI, patient retention, practitioner performance, and more. Learn how to enable them inside ClinicSync Pro and GoHighLevel.

Watch on YouTube →

Jane + GHL Full Integration Walkthrough

How to automate no-show follow-ups, reviews, reactivation, and enable 2-way calendar sync between Jane App and GoHighLevel — with real automations you can copy.

Watch on YouTube →

Cliniko + GHL Full Integration Walkthrough

ClinicSync Pro’s Cliniko integration: reminders, no-show/cancellation follow-up, AI booking, and advanced reactivation — real snapshot demo and best practices.

Watch on YouTube →

PT Everywhere + GHL Integration

Automate your PT clinic: see how all custom fields sync, how to build automations for reminders, reactivation, and reviews with PT Everywhere and GHL.

Watch on YouTube →

Voice AI Booking with GHL + EMR

How to connect Jane or Cliniko calendars to GoHighLevel for real-time Voice AI booking — perfect for agencies and clinics wanting automated phone bookings.

Watch on YouTube →

Ready-to-Use GHL Snapshots

Instantly clone our recommended GoHighLevel snapshot for your EMR and automation setup. Click below to download the exact workflows, custom fields, and pipelines we demo in our videos. (You must be logged into your GHL account to install.)

ROI Dashboard (Add-On)

For clinics/agencies: add full ROI reporting to any sub-account. $15/mo per location.Download Snapshot

Jane Integration Snapshot

All automations and custom fields for Jane + GHL.Download Snapshot

PtEverywhere Integration Snapshot

Custom fields and automations for PT clinics using PtEverywhere.Download Snapshot

Cliniko Integration Snapshot

Prebuilt GHL setup for Cliniko + automations.Download Snapshot

Nookal Integration Snapshot

Prebuilt GHL setup for Nookal + automations.Download Snapshot

PromptEMR Integration Snapshot

Prebuilt GHL setup for PromptEMR + automations.Download Snapshot

Tip: If you need help installing or customizing any snapshot, book a 1:1 call or join the weekly Q&A above!

Data Security & Privacy

All sync traffic and credentials are protected with bank-grade encryption. No passwords stored in plain text.
Each clinic’s syncs are isolated. No cross-tenant access possible.
HIPAA, PIPEDA, and GDPR aligned. You control your data — we never sell or share it.

Troubleshooting & Support

Sync status and errors are shown in your dashboard for every location. If you see an error about cookies or 2FA, re-sync your credentials and make sure two-factor is disabled.
Still stuck? Book a 1:1 session or email hello@clinicsyncpro.com.

FAQ

How often does it sync? Every 5–30 minutes depending on volume and load. Most clinics see updates in under 5 minutes.
Can I use more than one platform? Yes, just add new connections for each location/platform.
Can you migrate me from another system? Yes! Use the help section in your dashboard to book onboarding.
Where can I see all the fields? Use the live mapping sheet above.

Important: Enable AI Booking Access First

Your location must have AI Booking enabled in ClinicSync Pro.
If you see a "not enabled for booking" error, go to your dashboard and enable AI Booking, or contact support for access.
Each API key only works for the linked location it was issued for.

Need help? Email hello@clinicsyncpro.com to get AI Booking enabled for your account.

Jane API Endpoints – Book, Update, and Cancel Appointments

Authentication

All endpoints require the x-api-key header. Find your API key in your dashboard under “Manage API / Webhooks.”

Each API key is mapped to a specific Jane-connected location. You cannot book for another location with your key.

Book Appointment

POST https://jane-api.clinikoconnect.com/api-book-appointment

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /api-book-appointment
Host: jane-api.clinikoconnect.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "customData": {
    "staff_member": "practitioner@email.com",
    "treatment_name": "Physio Consult",
    "clinic_location_name": "Pitt St Clinic",
    "roomName": "Room 2"
  },
  "calendar": {
    "startTime": "2024-08-02T10:00:00Z",
    "endTime": "2024-08-02T10:30:00Z",
    "selectedTimezone": "Australia/Sydney",
    "appointmentId": "abc123-xyz"
  },
  "first_name": "Sam",
  "last_name": "Smith",
  "email": "sam.smith@example.com",
  "phone": "+61400000000"
  // city, state, country optional
}

Note: The location field is not required; it is set by your API key automatically.

Success Response:

{
  "message": "Appointment booked successfully",
  "bookedAppointment": { /* Jane appointment object */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Required booking fields missing.
422 Unprocessable Entity: Invalid staff, treatment, or time.
500: Server error (try again or contact support).

Update (Reschedule) Appointment

POST https://jane-api.clinikoconnect.com/api-update-appointment

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /api-update-appointment
Host: jane-api.clinikoconnect.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "calendar": {
    "appointmentId": "abc123-xyz",
    "startTime": "2024-08-02T12:00:00Z",
    "endTime": "2024-08-02T12:30:00Z",
    "selectedTimezone": "Australia/Sydney"
  }
}

Success Response:

{
  "success": true,
  "appointment": { /* Updated Jane appointment object */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Required fields missing.
404 Not Found: Appointment not found.
422 Unprocessable Entity: Update failed (check new times, or try again).

Cancel Appointment

POST https://jane-api.clinikoconnect.com/api-cancel-appointment

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /jane-api.clinikoconnect.com
Host: api-sync.clinicsyncpro.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "appointmentId": "abc123-xyz",
  "cancelled_reason": "Patient requested cancellation",
  "with_notifications": true,
  "send_wlns": true
}

Tip: calendar.appointmentId is also accepted.

Success Response:

{
  "success": true,
  "appointment": { /* Jane appointment cancellation response */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Required cancel fields missing.
404 Not Found: Appointment not found.
422 Unprocessable Entity: Cancel failed (already cancelled, or wrong id).

Webhook Payload: Jane Patient Update

When a patient is created or updated, your webhook receives a JSON body with all the following fields:
View full live sync field map →

View Example Payload


{
  "firstName": "Sam",
  "lastName": "Smith",
  "email": "sam.smith@example.com",
  ...
}

Note: All fields and mapping are kept up to date in the Sync Field Map. You can use any field in your Zapier, Make, or custom automation logic.

Note: All appointment endpoints are fully isolated by API key/location.
Need additional fields or help? Contact us.

Important: Enable AI Booking Access First

Your location must have AI Booking enabled in ClinicSync Pro.
If you see a "not enabled for booking" error, go to your dashboard and enable AI Booking, or contact support for access.
Each API key only works for the linked location it was issued for.

Need help? Email hello@clinicsyncpro.com to get AI Booking enabled for your account.

Cliniko API Endpoints – Book, Update, and Cancel Appointments

Authentication

All endpoints require the x-api-key header, found in your dashboard under “Manage API / Webhooks”.

Each API key is mapped to a specific Cliniko-connected location. You cannot book for another clinic with your key.

Book Appointment

POST https://cliniko-api.clinikoconnect.com/api-book-appointment

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /api-book-appointment
Host: cliniko-api.clinikoconnect.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "customData": {
    "staff_member": "practitioner@email.com",
    "appt_type_name": "Physio Consult",
    "appt_type_category": "Physiotherapy",
    "appt_type_duration": "30",
    "business_name": "Downtown Health"
  },
  "calendar": {
    "startTime": "2024-08-02T10:00:00Z",
    "endTime": "2024-08-02T10:30:00Z",
    "selectedTimezone": "Australia/Sydney",
    "appointmentId": "abc123-xyz"
  },
  "first_name": "Sam",
  "last_name": "Smith",
  "email": "sam.smith@example.com",
  "phone": "+61400000000"
}

Note: The location field is not required; it is auto-injected based on your API key.

Success Response:

{
  "success": true,
  "appointment": { /* Cliniko appointment object */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Required booking fields missing.
422 Unprocessable Entity: Invalid practitioner, appointment type, or business name.
500: Unhandled errors (try again, or contact support).

Update Appointment

POST https://cliniko-api.clinikoconnect.com/api-update-appointment

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /api-update-appointment
Host: cliniko-api.clinikoconnect.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "calendar": {
    "appointmentId": "abc123-xyz",
    "startTime": "2024-08-02T11:00:00Z",
    "endTime": "2024-08-02T11:30:00Z",
    "selectedTimezone": "Australia/Sydney"
  }
}

Success Response:

{
  "success": true,
  "appointment": { /* Updated Cliniko appointment object */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Required update fields missing.
404 Not Found: Appointment not found.
422 Unprocessable Entity: Appointment could not be updated (check times, or try again).

Cancel Appointment

POST https://cliniko-api.clinikoconnect.com/api-cancel-appointment

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /api-cancel-appointment
Host: cliniko-api.clinikoconnect.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "appointmentId": "abc123-xyz",
  "cancellation_note": "Client requested cancellation",
  "cancellation_reason": 50
}

Success Response:

{
  "success": true,
  "appointment": { /* Cliniko appointment cancellation response */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Required cancel fields missing.
404 Not Found: Appointment not found.
422 Unprocessable Entity: Appointment could not be cancelled (already cancelled, wrong id, etc).

Webhook Payload: Cliniko Patient Update

When a patient is created or updated, your webhook receives a JSON body with all the following fields:

View Example Payload

{
  "firstName": "Sam",
  "lastName": "Smith",
  "email": "sam.smith@example.com",
  "phone": "+61400000000",
  "dateOfBirth": "1990-01-01",
  "state": "NSW",
  "city": "Sydney",
  "upcoming_appointment_cancelled_at": "...",
  "upcoming_appointment_cancellation_reason": "...",
  "upcoming_appointment_name": "...",
  "last_appointment_name": "...",
  "last_updated_date_via_api": "...",
  "last_appointment_cancelled_at": "...",
  "last_appointment_did_not_arrive": "...",
  "last_appointment_cancellation_reason": "...",
  "upcoming_appointment_reminder_start_time": "...",
  "patient_id": "123456",
  "upcoming_appointment_start_time": "...",
  "upcoming_appointment_business_name": "...",
  "upcoming_appointment_practitioner_name": "...",
  "upcoming_appointment_type": "...",
  "upcoming_appointment_counts": 1,
  "accepted_email_marketing": "Yes/No",
  "accepted_sms_marketing": "Yes/No",
  "total_amount_spent": 1000,
  "total_amount_spent_this_month": 200,
  "total_number_of_appointments": 15,
  "last_appointment_start_time": "...",
  "last_appointment_business_name": "...",
  "last_appointment_practitioner_name": "...",
  "last_appointment_type": "..."
}

Note: All fields and mapping are kept up to date in the Sync Field Map. You can use any field in your Zapier, Make, or custom automation logic.

Note: All appointment endpoints are fully isolated by API key/location. Need more fields or support? Contact us.

PtEverywhere API Endpoints – Patient Sync (Appointments Coming Soon)

Authentication

All endpoints require the x-api-key header, found in your dashboard under “Manage API / Webhooks”.

Each API key is mapped to a specific PT Everywhere location. You cannot sync for another location with your key.

Webhook Payload: PtE Patient Update

When a patient is created or updated in PtEverywhere, your webhook receives the following JSON fields:

View Example Payload

{
  "last_updated_date_via_api": "...",
  "TotalNumberOfVisits": 10,
  "PatientId": "12345",
  "Age": 36,
  "LastSeenBy": "Dr. Lee",
  "LastVisit": "2024-05-10",
  "NextVisit": "2024-08-05",
  "Service": "Initial Consultation",
  "LastVisit_serviceName": "Manual Therapy",
  "LastVisit_locationName": "Downtown Clinic",
  "LastVisit_provider": "Dr. Lee",
  "LastVisit_status": "Completed",
  "NextVisit_serviceName": "Follow Up",
  "NextVisit_locationName": "Downtown Clinic",
  "NextVisit_provider": "Dr. Smith",
  "NextVisit_status": "Scheduled",
  "NextVisit_apptReminder_startTime": "2024-08-05T09:00:00Z",
  "FirstAppt": "2021-10-15",
  "TotalRevenue": 1700,
  "TotalCollected": 1500,
  "Primary_payer": "Medicare",
  "Secondary_payer": "Bupa",
  "Tertiary_payer": null,
  "firstName": "Sam",
  "lastName": "Smith",
  "email": "sam.smith@example.com",
  "phone": "+61400000000",
  "dateOfBirth": "1990-01-01",
  "state": "NSW",
  "city": "Sydney"
}

Note: Appointment Booking APIs are coming soon for PtEverywhere. For the most up-to-date field mappings, see the Sync Field Map.

Note: All endpoints are fully isolated by API key/location. Need more fields or support? Contact us.

PromptEMR API Endpoints – Patient & Appointment Sync

Authentication

All endpoints require the x-api-key header, found in your dashboard under “Manage API / Webhooks”.

Each API key is mapped to a specific PromptEMR location. You cannot sync for another location with your key.

Webhook Payload: PromptEMR Patient Update

When a patient or appointment is created or updated in PromptEMR, your webhook receives the following JSON fields:

View Example Payload

{
  "firstName": "Sam",
  "lastName": "Smith",
  "name": "Sam Smith",
  "email": "sam.smith@example.com",
  "phone": "+61400000000",
  "dateOfBirth": "1990-01-01",
  "locationId": "abc123",
  // Custom fields
  "upcoming_appt_reminder_start_time": "2024-08-05T09:00:00Z",
  "last_appt_date": "2024-07-28",
  "last_appt_location": "Sydney Clinic",
  "last_appt_provider": "Dr. Lee",
  "last_appt_service": "Initial Consultation",
  "upcoming_appt_date": "2024-08-05",
  "upcoming_appt_location": "Sydney Clinic",
  "upcoming_appt_provider": "Dr. Smith",
  "upcoming_appt_service": "Follow Up",
  "last_updated_date_via_api": "2024-08-01"
}

Note: For the most up-to-date field mappings, see the Sync Field Map.

Note: All endpoints are fully isolated by API key/location. Need more fields or support? Contact us.

Important: Enable AI Booking Access First

Your connection must have AI Booking enabled in ClinicSync Pro.
If you see a "not enabled for booking" error, go to your dashboard and enable AI Booking, or contact support for access.
Each API key only works for the linked location it was issued for.

Need help? Email hello@clinicsyncpro.com to get AI Booking enabled for your account.

Nookal API Endpoints – Book, Update, and Cancel Appointments

Authentication

All endpoints require the x-api-key header, found in your dashboard under “Manage API / Webhooks”.

Each API key is mapped to a specific Nookal-connected location. You cannot book for another location with your key.
Your connection must have AI Booking enabled in ClinicSync Pro.

Book Appointment

POST https://nookal-api.clinikoconnect.com/api/nookal/book_appt

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /api/nookal/book_appt
Host: nookal-api.clinikoconnect.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "customData": {
    "locationName": "Parramatta Physio",
    "region": "AU",
    "basicKey": "YOUR_NOOKAL_BASIC_KEY",
    "serviceCode": "PHYSIO30",
    "practitionerName": "Dr. Jane Doe"
  },
  "calendar": {
    "startTime": "2024-08-02T10:00:00Z",
    "appointmentId": "abc123-xyz"
  },
  "patientFirstName": "Sam",
  "patientLastName": "Smith",
  "patientDOB": "1990-01-01",
  "patientEmail": "sam.smith@example.com",
  "patientMobile": "+61400000000"
}

Note: locationName, region, and basicKey are auto-injected if you use the API key from the dashboard.

Success Response:

{
  "success": true,
  "apptID": 123456,
  "appointment": { /* Nookal appointment object */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Missing required fields.
422 Unprocessable Entity: Invalid practitioner, service code, or time.
500: Server error (try again, or contact support).

Update (Reschedule) Appointment

POST https://nookal-api.clinikoconnect.com/api/nookal/update_appt

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /api/nookal/update_appt
Host: nookal-api.clinikoconnect.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "calendar": {
    "appointmentId": "123456",
    "startTime": "2024-08-02T11:00:00Z"
  }
}

Success Response:

{
  "success": true,
  "updated": { /* Updated Nookal appointment object */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Required fields missing.
404 Not Found: Appointment not found.
422 Unprocessable Entity: Update failed (invalid times, or already canceled).

Cancel Appointment

POST https://nookal-api.clinikoconnect.com/api/nookal/cancel_appt

Required headers: x-api-key and Content-Type: application/json

Request Example:

POST /api/nookal/cancel_appt
Host: nookal-api.clinikoconnect.com
x-api-key: YOUR_API_KEY_HERE
Content-Type: application/json

{
  "appointmentId": "123456"
}

Success Response:

{
  "success": true,
  "canceled": { /* Nookal appointment cancellation object */ }
}

Common Errors:

401 Unauthorized: API key missing or invalid.
400 Bad Request: Required cancel fields missing.
404 Not Found: Appointment not found.
422 Unprocessable Entity: Cancel failed (already canceled, or wrong id).

Webhook Payload: Nookal Patient & Appointment Update

When a patient or appointment is updated in Nookal, your webhook receives a JSON payload with the following fields (example below):

View Example Payload

{
  "last_updated_date_via_api": "2024-07-31",
  "patient_id": "123456",
  "firstName": "Sam",
  "lastName": "Smith",
  "email": "sam.smith@example.com",
  "phone": "+61400000000",
  "dateOfBirth": "1990-01-01",
  "state": "NSW",
  "city": "Sydney",
  "gender": "Female",
  "address1": "123 Main St",
  "postalCode": "2000",
  "appointments_count": 15,
  "last_appt_arrived": "2024-07-20T10:00:00Z",
  "last_appt_dna": null,
  "last_appt_cancelled": "2024-07-10T09:30:00Z",
  "last_appt_cancellationDate": "2024-07-10",
  "last_appt_practitioner_name": "Dr. Jane Doe",
  "last_appt_type": "Physio Consult",
  "last_appt_location": "Parramatta Physio",
  "last_appt_date": "2024-07-20",
  "upcoming_appt_type": "Follow Up",
  "upcoming_appt_location": "Parramatta Physio",
  "upcoming_appt_date": "2024-08-02",
  "upcoming_appt_practitioner_name": "Dr. Jane Doe",
  "upcoming_appt_reminder_time": "2024-08-02T09:00:00Z",
  "total_amount_paid": 1200,
  "total_unpaid_balance": 0
}

Note: The full list of available fields is always up to date in the Sync Field Map.

Tip: All endpoints are fully isolated by API key/location. For help, contact hello@clinicsyncpro.com.

Join Our Weekly Live Q&A!

Every Tuesday at 3pm PST, Siavash hosts a live Zoom meeting for all ClinicSync Pro users, agency partners, and anyone considering our platform.

Bring your questions, get help with automations, or see live demos of new features. It's the best way to get expert support, network with other clinics and agencies, and learn how to get even more value from ClinicSync Pro.

Join Weekly Zoom Meeting

No registration required. Just click the link and drop in on Tuesdays at 3pm PST!

More tutorials and snapshot downloads coming soon.
Need something not covered here? Contact us.