The calendar on our website matches the rest of the site, loads with the page and tells us where every booking came from. Every appointment still lands in GoHighLevel, and GoHighLevel still sends the confirmations and runs the workflows. Here is how it works, what caught us out, and when the standard embed is the better choice.

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 embed | Our own widget | |
|---|---|---|
| Looks like | GoHighLevel’s booking page, in a frame | Your site: same fonts, colors and layout |
| Where a booking came from | Not recorded on the contact | A from-<channel> tag, and Source on new contacts |
| Confirmations, reminders, workflows | GoHighLevel sends and runs them | Still GoHighLevel, unchanged |
| Setup | Paste one embed code | A small service to build, host and look after |
| If something breaks | GoHighLevel fixes it | You fix it, so it needs a fallback |
Three parts: the widget on the page, a small service on Cloudflare Workers that holds the GoHighLevel key, and GoHighLevel itself.
The widget asks our service for open times, in the visitor’s own time zone.
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.
Before booking, the service checks that exact time with GoHighLevel again, live, so two people can’t take the same slot.
It creates or updates the contact, adds tags for the booking and the channel, and sets Source only if the contact is new.
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.
Confirmation emails, reminders and any workflow on the calendar or the tags run as normal.

Seven calls to GoHighLevel’s API version 2, made with a private integration token that stays on the server.
| Call | What it’s for |
|---|---|
GET /calendars/{id} | The calendar’s name, slot length and invite title |
GET /calendars/{id}/free-slots | Open start times between two dates, asked for in UTC |
POST /contacts/upsert | Create the contact, or update one with the same email or phone |
POST /contacts/{id}/tags | Add tags without removing the ones already there |
PUT /contacts/{id} | Set Source on a contact that is new |
POST /calendars/events/appointments | Book the time, confirmed, with notifications on |
POST /contacts/{id}/notes | Record 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.
The part the embed couldn’t do, and the reason we built it.
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.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 calendarA HIPAA-ready integration hub for an agency that white-labels GoHighLevel for membership-based primary care practices. It is live, and we run 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.

“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.”
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