Which calendars does Leadlock book into, and how?
| Calendar | How it connects | Availability check | Booking |
|---|---|---|---|
| GoHighLevel | Native. Connect the account and pick the calendar on the agent. | Built in. | Booked on the call, on the contact already in GoHighLevel. |
| Google Calendar | Custom function on the Google Calendar API. Not native. | Your endpoint runs a free and busy query for the date. | Your endpoint creates the event. Booked on the call. |
| ServiceTitan | Two custom functions on the ServiceTitan API. | Open arrival windows for the date. | A booking request the office confirms. |
| Outlook, Calendly, Cal.com | Not native. Each has an API, so a custom function can reach it. | Whatever your endpoint returns. | Whatever your endpoint creates. |
What does the agent read and write in Google Calendar?
Reads: the busy blocks on the calendar for the date the caller asks about. Google's API calls this a free/busy query. Your endpoint turns the gaps into open times and returns them as JSON.
Writes: one event at the time the caller picks. Google's API calls this an event insert. The event carries what you put in the function schema: the caller's name, phone, address and a short note. Add the caller's email as an attendee and Google can send the invite.
The agent can only do what those two functions allow. The Google credentials stay on your endpoint, and Leadlock never sees them.
How do you set it up?
-
Give an endpoint access to the calendar
Use the Google Calendar API from a small service you control, or a Make, Zapier or n8n workflow with a webhook trigger.
-
Create the availability function
One required parameter: the date. The description tells the agent to always check before it offers a time.
-
Create the booking function
Date, start time and name are required. Add phone, email, address and a summary as the business needs.
-
Attach both and add the prompt rule
Attach the functions to the agent. In the prompt, tell it to check availability first and to read the time back before it books.
-
Test, then go live
The function test sends a real request, so it creates a real event. Delete it, then make a call and book a slot yourself.
How long does it take? The Leadlock side is minutes: a self-serve agent is live in about 5 minutes, and each function is a name, a description, a parameter schema and a URL. The endpoint or workflow that talks to Google is the part that varies. The pattern, with real schemas, is in the ServiceTitan booking recipe.