Book a Discovery Call
The short version
  • Why we built it: the standard GoHighLevel calendar is an embedded frame. It looks like GoHighLevel rather than your site, and it can’t tell you which channel a booking came from.
  • How it works: a small service on Cloudflare Workers sits between our calendar widget and GoHighLevel’s API, so the API key never reaches the browser.
  • GoHighLevel still does the rest: confirmations, reminders and workflows run exactly as they did with the embed.
  • Every booking carries its source: the contact is tagged with the channel, such as from-ai-assistant, and a new contact’s Source reads like “AI assistant (chatgpt.com)”.
  • Built not to lose a lead: the time is re-checked live before booking, rate limits are retried, open times are cached with a spare copy, and if anything fails the visitor gets GoHighLevel’s own booking page.
A visitor seen over the shoulder picking a time on a booking calendar on a business website

Why not just embed the GoHighLevel calendar?

For most businesses, the embed is the right answer. We wanted two things it couldn’t give us: a booking step that looks like the rest of the site, and the channel behind every booking.

GoHighLevel embedOur own widget
Looks likeGoHighLevel’s booking page, in a frameYour site: same fonts, colors and layout
Where a booking came fromNot recorded on the contactA from-<channel> tag, and Source on new contacts
Confirmations, reminders, workflowsGoHighLevel sends and runs themStill GoHighLevel, unchanged
SetupPaste one embed codeA small service to build, host and look after
If something breaksGoHighLevel fixes itYou fix it, so it needs a fallback

How it works, step by step.

Three parts: the widget on the page, a small service on Cloudflare Workers that holds the GoHighLevel key, and GoHighLevel itself.

01
The visitor opens the calendar

The widget asks our service for open times, in the visitor’s own time zone.

02
Open times come from GoHighLevel

The service asks GoHighLevel for the calendar’s free slots in UTC, groups them by day in the visitor’s zone, and shares the answer with every visitor for 60 seconds.

03
The visitor picks a time

Before booking, the service checks that exact time with GoHighLevel again, live, so two people can’t take the same slot.

04
The contact is saved

It creates or updates the contact, adds tags for the booking and the channel, and sets Source only if the contact is new.

05
The appointment is booked

It books the time in the GoHighLevel calendar, confirmed and with notifications on, and adds a note: where they came from, the page they landed on and the page they booked from.

06
GoHighLevel takes over

Confirmation emails, reminders and any workflow on the calendar or the tags run as normal.

A developer seen from behind at two monitors, code on one and a calendar widget preview on the other

The GoHighLevel API calls it uses.

Seven calls to GoHighLevel’s API version 2, made with a private integration token that stays on the server.

CallWhat it’s for
GET /calendars/{id}The calendar’s name, slot length and invite title
GET /calendars/{id}/free-slotsOpen start times between two dates, asked for in UTC
POST /contacts/upsertCreate the contact, or update one with the same email or phone
POST /contacts/{id}/tagsAdd tags without removing the ones already there
PUT /contacts/{id}Set Source on a contact that is new
POST /calendars/events/appointmentsBook the time, confirmed, with notifications on
POST /contacts/{id}/notesRecord where the booking came from

Calendar calls send the Version: 2021-04-15 header and contact calls 2021-07-28. See HighLevel’s API documentation, and our integrations guide for the API’s limits.

Knowing where every booking came from.

The part the embed couldn’t do, and the reason we built it.

  • The site remembers the source for 30 days. On the first visit it keeps the tracking tags, the referring site, any ad click marker and the landing page, in the visitor’s own browser. No personal data is stored, and moving between our pages doesn’t overwrite it.
  • The booking turns it into a channel: LinkedIn, Instagram, Facebook, the GoHighLevel directory, Google Ads, search engines, AI assistants such as ChatGPT and Perplexity, email, other websites or direct visits.
  • GoHighLevel gets it three ways: a tag such as from-ai-assistant, a Source on new contacts such as “AI assistant (chatgpt.com)”, and a note with the landing page and the page they booked from.
  • What it told us: some of our discovery calls now start with a question to ChatGPT. Without the tag, they would have looked like direct visits.

What caught us out.

  • An upsert wipes tags and Source. GoHighLevel’s contact upsert replaces the tags and the Source of a contact that already exists. So tags go on through the separate tags call, and Source is set only when the contact is new, so a returning lead keeps the source they first came from.
  • Ask for free slots in UTC. One answer then serves visitors in every time zone, and you group the times into days in each visitor’s zone yourself. Long date ranges go in four-week pieces.
  • Never book from a cached time. The shared copy of open times can be up to a minute old. Re-check the exact slot live before booking, and if GoHighLevel is too busy to answer, book anyway: GoHighLevel checks the slot itself.
  • Expect rate limits. A 429 from GoHighLevel means the request wasn’t processed, so it is always safe to retry. We retry twice with a short pause, and retry server errors only on reads.
  • Keep a spare copy. Open times are cached for 60 seconds, with a spare kept for 15 minutes that is served only when GoHighLevel can’t answer.
  • Stop bots without a captcha. A hidden field people never fill, a minimum time on the form, and a limit on bookings per connection stop junk appointments without annoying real visitors.
  • Insist on a country code. Phone numbers are checked as international numbers before they reach GoHighLevel, so reminders by text reach the right country.
  • Always have a way out. If the service can’t load times or book, the widget shows a button to GoHighLevel’s own booking page, so no visitor leaves without a way to book.

Should you build your own?

  • Keep the embed if one calendar is enough, the booking page doesn’t need to match your site, and you don’t need the source on every booking.
  • Build your own if booking is the main thing your site asks for, you spend on ads or content and need to know what books calls, or you need logic the embed can’t do.
  • Either way, GoHighLevel stays the calendar, so your team, reminders and workflows don’t change.

The calendar further down this page is the one this guide describes. Book a Discovery Call on it and you’ll see the whole thing work.

Try the calendar

Common questions.

Yes. GoHighLevel's API gives you a calendar's free slots and lets you book appointments, so you can build your own calendar widget and keep GoHighLevel as the calendar behind it. Run the API calls from a small server-side service so your API key never reaches the browser.
Yes. When the appointment is booked through the API with notifications on, GoHighLevel sends its confirmations and reminders and runs the calendar's workflows, exactly as it does for a booking made through its own widget.
The calendar's free-slots endpoint for open times, the contact upsert to save the visitor, the tags endpoint to add tags, and the appointments endpoint to book. We also read the calendar's settings and add a note to the contact.
Never put it in your website's code. Our widget calls a small service on Cloudflare Workers, which holds the key and makes the GoHighLevel calls itself.
The upsert replaces the tags of a contact that already exists. Add tags with the separate tags endpoint after the upsert instead, and they are added to the ones the contact already has.
The site remembers the visitor's source for 30 days: tracking tags, the referring site and the page they landed on, with no personal data. The booking then adds a tag such as from-search or from-ai-assistant, and a new contact's Source says the channel and site.
Open times fall back to a spare copy kept for 15 minutes, and if booking still fails, the visitor is shown a button to GoHighLevel's own booking page, so no lead is lost.
Use the embed if one calendar is enough and you don't need to know where bookings come from. Build your own when the booking step has to look like your site, you need source tracking on every booking, or you want logic the embed can't do.

Every EHR update in the right GHL account within seconds.

A HIPAA-ready integration hub for an agency that white-labels GoHighLevel for membership-based primary care practices. It is live, and we run it.

Seconds
from a change in the EHR to an updated GHL record
Hourly
check that every practice can only reach its own account

Your site, your booking step. GoHighLevel behind it.

Book a free Discovery Call on the calendar below. We’ll look at how visitors book with you now and tell you whether the embed is enough or a custom widget would pay off.

Yvonne Dam
“Ethan transformed my business by consolidating everything into GHL. Far more organized, efficient, and easy to manage. Impressive attention to detail across everything he touched.”
Yvonne Dam, Founder, Advisor

Not ready for a call? Tell us how it works now, and we’ll send you a written build plan within 24 hours.

Get a free build plan instead