Fix: GoHighLevel calendar not syncing with Google Calendar
GHL's Google sync is three separate settings: the connection, the linked calendar and conflict calendars. Each breaks on its own with a different symptom. Here's how to tell which one you've got.
Symptoms — what you're seeing
- Appointments booked in GoHighLevel don't show up in Google Calendar
- Events you add in Google don't block time in GHL, so people book over them
- Google events show up in GHL as grey blocked slots, not as appointments with contacts
- Sync worked for weeks and then stopped, or the user's calendar tile has a red "Reconnect" banner
- Every appointment appears twice in Google
Why this happens
GHL's Google sync has three separate settings that people treat as one: the connection (the user's Google login), the linked calendar (the one Google calendar GHL writes bookings into, and optionally reads appointments from), and conflict calendars (Google calendars GHL only reads to block busy time). Each fails on its own, and each has a different symptom.
- The connection expired. A changed Google password, revoked access, or a security review breaks the OAuth link. GHL shows a red "Reconnect" banner on the connection and silently stops syncing.
- No linked calendar, or write-back is off. Connecting Google isn't enough. If no linked calendar is chosen, or "Write Back Appointments" is off, GHL bookings never reach Google.
- The calendar isn't a conflict calendar. Google events only block GHL availability if that Google calendar is enabled as a conflict calendar, and only events marked Busy count. Events marked Free leave the slot bookable.
- One-way sync is working as designed. In the default mode, Google events come into GHL as blocked slots: no contact, no workflow. Turning them into real GHL appointments needs two-way sync.
- It's per user. Each team member connects their own Google account. On a round-robin calendar, the one user who never connected (or lost writer access) is the one whose bookings don't sync.
The fix, step by step
- Check the connection for each user. Go to Settings → Calendars → Connections as that user. A red banner or red-outlined tile means the authorisation expired: click Reconnect and sign in again, granting both read and write access. After reconnecting, unsynced upcoming appointments are pushed automatically. If Google says the calendar was deleted, use Fix This → Remove Deleted Calendars.
- Set a linked calendar and turn on write-back. Under Linked Calendar, click Add, pick the user's main work calendar, and save. Then check that Write Back Appointments is on. The user needs writer access to that Google calendar, or it won't appear as an option.
- Choose the sync direction you actually want. In the linked calendar's advanced settings, pick one-way if Google events should only block time, or two-way if events created in Google should become GHL appointments (with contacts created and workflows able to fire). Two-way means a personal "dentist" event in Google becomes a GHL appointment, so use it only on work calendars.
- Enable conflict calendars for availability. Under Conflict Calendars, click Edit and switch on every Google calendar that should block booking time, including personal ones if needed. Check that the blocking events are marked Busy in Google.
- Fix duplicates by writing back to one calendar only. Duplicate events almost always mean write-back is on for more than one calendar. Keep write-back on the primary work calendar and use other calendars as conflict calendars only.
- Align time zones, then test. The Google calendar's time zone, the GHL user profile time zone and the GHL calendar's time zone should match. Then book a test appointment in GHL and check it appears in Google within a minute or two, and add a Busy event in Google and check the slot disappears from the booking widget.
Common variations
- "Google events show in GHL but people still book over them" — the calendar is syncing events but isn't enabled as a conflict calendar, or the events are marked Free.
- "Google events appear in GHL but no contact or workflow" — that's one-way sync behaving correctly. Switch to two-way if you need them as real appointments.
- "It works for me but not for one teammate" — sync is per user. That person needs to connect their own Google account and set their own linked calendar.
- "Showed / No Show status isn't in Google" — those status changes aren't written back. New bookings, cancellations and reschedules are.
- "Appointments land an hour off" — time zones don't match, or one of them doesn't follow daylight saving. Align all three.
When this isn't the issue
- If the booking widget shows no slots at all, or booking fails with an error, that's GHL availability, not Google — see GoHighLevel calendar booking stopped working.
- If appointments sync but the confirmation workflow doesn't run, see GHL workflow not triggering.
- If you're syncing GHL bookings into another system (Boulevard, Jobber, a custom app), that needs webhooks or the API, not Google sync — see Supabase Edge Function for GHL bookings.
Need bookings to land in more than one place reliably? Tell me what you're syncing — calendar plumbing between GHL and other tools is a common build.
Need this workflow customized or debugged? Book a 30-min scope call →
Stuck configuring this workflow?
I build and fix n8n workflows for agencies and SaaS teams. 30-minute scope call — bring the problem, leave with an estimate.