GoHighLevel Calendar Sync: Google and Outlook Setup

GoHighLevel calendar sync keeps a rep's booking calendar and their personal Google or Outlook calendar pointed at the same truth, so a client can't grab a slot that's already taken somewhere else.

The connection sits between one HighLevel user's profile and one external calendar account. Once it's live, bookings write into the external calendar, and events already sitting there block new availability back inside HighLevel.

What GoHighLevel calendar sync actually connects

Google Calendar gets the fuller treatment. HighLevel's own setup guide describes real-time, two-way sync: book an appointment in HighLevel and it lands in Google Calendar within moments. An event added directly in Google blocks that same slot back in HighLevel.

The connection also includes automatic catch-up syncing, so appointments created while a user was briefly disconnected still come through once the link is restored.

Granting access means full read and write, or "writer", permission, not just viewing rights, since the sync has to create, move and cancel events on both sides. It's a per-user connection rather than a sub-account setting, so each team member links their own Google account.

Outlook sync comes with a plan restriction

The same two-way idea applies to a primary Outlook calendar, but with real limits worth knowing before promising a client it'll work. Outlook integration is exclusive to the Unlimited and Agency Pro plans, so a Starter subscription doesn't get it at all.

It only works with Round Robin, Collective and Service calendars, never a plain one-on-one booking calendar, which lines up with how each GoHighLevel calendar type handles availability differently in the first place.

Capability	Google Calendar	Outlook
Sync direction	Two-way	Two-way on the primary calendar
Plan availability	All plans	Unlimited ($297/mo) and Agency Pro ($497/mo) only
Supported accounts	Personal Gmail, G Suite	Office 365, Outlook.com, Live.com, Hotmail
Connection limit	Per user	One Outlook account per user, no sharing

HighLevel can't write to a Google and an Outlook calendar for the same person at once. The two are an either-or choice per team member, not something you stack.

Linked calendars and conflict calendars aren't the same thing

A linked calendar and a conflict calendar sound interchangeable. They aren't. A linked calendar is the one HighLevel writes bookings into, the calendar a client's appointment actually lands on.

A conflict calendar, also called a check-for-availability calendar, is read-only. HighLevel reads its busy blocks and marks those slots unavailable without ever writing anything back to it.

Link a personal calendar for bookings and add a shared team calendar as a conflict calendar, and a staff meeting on the shared calendar blocks the slot without the client's appointment ever showing up there. Skip that step, and HighLevel will book straight over it.

When sync breaks, the troubleshooting tool finds it fast

Sync problems are rarely random. Most trace back to an expired or revoked OAuth token, a calendar edited mid-sync, or an appointment assigned to someone who never connected a calendar at all.

HighLevel's built-in troubleshooting tool, reachable from Calendar Settings or the wrench icon beside any calendar, narrows that down without a support ticket.

Open it, pick a date, and hover over an unavailable slot. A tooltip names the reason with a status code such as USER, CONFLICT, BOOKED, BLOCKED or BUFFER, pointing straight at whether the problem is a missing connection, a genuine conflict, or a buffer window eating the slot.

For an agency running this across a dozen client accounts, the per-user connection model on both sides means it isn't a set-and-forget onboarding step.

Building the connection check into new-hire setup, the kind of workflow automation we build as part of GHL setup and configuration, catches a missing calendar link before the first client ever lands on it.

It's also the detail white-label agencies managing sync across client sub-accounts run into most, covered in our white-label support work.

Cover photo by Pixabay on Pexels