You already live in Google Calendar. Your appointments are there, so is the dentist on Thursday, and so is the afternoon you blocked for paperwork. Now you want an assistant that books customers for you, and the obvious worry is that it will book someone straight over the top of something you put in Google yourself.
That is the problem Google Calendar AI booking in Klugon is meant to reduce. Once connected, the assistant can ask Google whether a time is busy before it confirms, and it can copy a booking into your Google Calendar as an event. It does this through a set of calendar tools in text conversations: the chat widget on your website and the messaging channels.
This page is deliberately precise, because "syncs with Google Calendar" can mean many things. Below you will find what data goes where, the setup steps exactly as they appear in the dashboard, which plan you need, and a plain list of what the connection does not do. The short version: Klugon's own Bookings page stays the source of truth, Google is checked and written to only in specific situations, and phone calls don't use the Google connection at all.
How Google Calendar AI booking works in Klugon
Klugon has its own booking calendar. When you set up services, opening hours, staff and booking rules, the assistant uses those to find free slots and to write bookings into Klugon's Bookings list. That part works without any outside calendar, across website chat, messaging and phone calls. It is described in full on the AI appointment booking page.
Connecting Google Calendar adds a second layer on top. It does not replace Klugon's calendar, and it does not turn Google into the place where bookings live. It gives the assistant two extra abilities in text conversations:
- Checking a time against Google. A tool called
check_availabilitylooks first at Klugon's own bookings for that date. If there is no clash there, it asks Google for the busy times on your connected calendar for the same window. If Google says the time is busy, the slot is reported as unavailable. - Copying a booking into Google. A tool called
create_calendar_eventcan add the appointment to your Google Calendar as an event. The copy only happens when the assistant asks for it in that call. There is a setting on the tool for this and it defaults to off, so it is not guaranteed for every booking.
If an event was copied to Google and the booking is later moved or cancelled through the same calendar tools, Klugon updates or deletes the Google event too, because it keeps the Google event ID.
What data goes from Klugon to Google
When the assistant copies a booking to Google Calendar, the event contains:
| Event field in Google | What Klugon puts there |
|---|---|
| Title | The title the assistant gives the event |
| Start and end time | The booked date and time, converted using your business time zone, and the duration |
| Description | "Customer:" followed by the customer's name, plus any notes from the conversation |
Nothing else is sent. Klugon does not invite the customer as a guest, attach a video-call link, set a colour or add reminders to the event. Google's own default notifications on your calendar still apply to you, as they do for any event.
What data comes from Google to Klugon
Klugon asks Google one question: is this calendar busy between these two times? Google answers with busy periods only. Klugon does not read the titles, descriptions, attendees or locations of your Google events, and it does not import them into Klugon's Bookings list. Your Google appointments therefore never show up as bookings in the Klugon dashboard.
That has a practical upside. You can share the calendar so the assistant sees free/busy only, if you do not want event details exposed at all, though you then lose the ability to copy bookings in (more on permissions in the setup section).
Where the bookings live
Every booking the assistant takes is stored in Klugon's Bookings list first. That is where you edit, cancel or delete bookings, and where the conflict check for future bookings happens. Google Calendar is a copy at best. If you delete an event in Google, Klugon is not told, and the booking stays in Klugon. If you move something in Google, Klugon does not move its booking.
So the honest rule is: treat Klugon's Bookings page as the diary of record, and Google Calendar as a place you can see busy times and, sometimes, copies.
Which conversations use the Google connection
The calendar tools run in Klugon's chat engine, which handles:
- the AI chatbot on your website;
- WhatsApp, Instagram, Messenger and Telegram conversations, such as those described on the WhatsApp AI chatbot page.
They are part of the booking toolset, so the assistant needs appointment booking switched on. If you have hand-picked the assistant's tool groups in its settings, the group called "Google Calendar" has to be on as well.
Phone calls do not use the Google connection. Klugon's AI phone receptionist books through Klugon's own slot finder and booking tool, which read Klugon's calendar only. On a call, the assistant does not ask Google whether you are busy and does not copy the booking into Google. If most of your bookings arrive by phone, Google Calendar will not see them unless you add them yourself or use another route, such as an automation through Zapier triggered by Klugon's booking event.
Setting up Google Calendar AI booking
Klugon connects to Google with a service account, not with a "Sign in with Google" button. A service account is a non-human account that belongs to a Google Cloud project. You create it, download its key, share your calendar with it, and paste the key into Klugon. It sounds technical, but you only do it once.
Before you start
You will need:
- a Google account with access to Google Cloud Console (a personal Google account works; so does Google Workspace);
- permission to create a project or use an existing one;
- the Google Calendar you want the assistant to check, and permission to change its sharing settings;
- a Klugon voice or social plan on the Business tier or higher (see the plan section below).
If your company uses Google Workspace, an administrator may have blocked the creation of service account keys. Google's documentation notes that organisations created on or after 3 May 2024 have that restriction enforced by default. If you hit an error when creating the key, that is the likely reason, and your Workspace or Cloud administrator will need to make an exemption for the project. Google explains the policy on its page about creating and deleting service account keys.
Step 1: create the service account and key in Google Cloud
The Klugon dashboard's first step reads: "In Google Cloud Console, create a service account and download the JSON key." In practice that means:
- Open Google Cloud Console and select or create a project.
- Turn on the Google Calendar API for that project. Klugon's step list doesn't spell this out, but Google requires it before a project can call the Calendar API. Google's help page on enabling and disabling APIs shows where: APIs and services, then Library, then search for the API and press Enable.
- Create a service account. Google's guide to creating service accounts walks through it: give it a name, and you can skip the optional role and access steps for this use.
- Open the new service account, go to its Keys tab, choose to add a key, pick JSON and create it. The file downloads once and cannot be downloaded again, so keep it somewhere safe.
Inside the JSON file there is a field called client_email. It looks like an email address ending in iam.gserviceaccount.com. You need it in the next step.
Step 2: share your calendar with the service account
The dashboard's second step reads: "Share your Google Calendar with the service account email (give it 'Make changes to events' permission)."
In Google Calendar on a computer, open the settings for the calendar, go to the section for sharing with specific people, add the service account's email address and choose the access level. Google's article on sharing your calendar shows the exact screens.
Which access level to choose depends on what you want:
| You want the assistant to | Choose in Google |
|---|---|
| Check busy times and copy bookings into Google | A level that allows making changes to events |
| Check busy times only | See only free/busy |
The dashboard recommends the "make changes" level because without it, any attempt to copy a booking into Google fails. With free/busy only, busy-time checks still work.
Step 3: copy the calendar ID
In the same calendar settings in Google, scroll to the section headed "Integrate calendar". The calendar ID is listed there. For your main calendar it is usually your Gmail or Workspace address. For other calendars it is a long string ending in group.calendar.google.com.
Step 4: connect it in Klugon
- In the Klugon dashboard, open Integrations.
- Find Google Calendar, either by searching or by choosing the Calendar filter.
- Click Connect. A panel opens with two fields and a collapsible Setup Guide that repeats the steps above.
- Paste the whole contents of the JSON key file into Service Account JSON.
- Paste the calendar ID into Calendar ID.
- Save.
Klugon masks the key when you come back to the panel. Note that it does not test the key when you save. The first real test is the next time the assistant checks a time. To check it yourself, open your website chat, ask for a slot at a time you have blocked in Google, and see whether the assistant says it is unavailable.
Once connected, the card shows Configure, and you can use Update Credentials to paste a new key or Disconnect to remove the connection.
Step 5: check the assistant's settings
In the assistant's settings, make sure appointment booking is on. If you have previously customised which tool groups the assistant can use, switch on the group called "Google Calendar", whose description reads "Check and add events when Google Calendar is connected in Integrations." If you have never touched those tool groups, all of them are available by default.
Which plan includes Google Calendar AI booking
Calendar connections are part of the feature Klugon's billing calls "Google Calendar, HubSpot and Zoho sync". It is included on:
- Voice plans: Business ($299 a month) and Scale ($499 a month);
- Social plans (WhatsApp, Instagram, Messenger and Telegram): Business ($249 a month) and Scale ($449 a month).
It is not included in any of the chat widget plans, and not on any Starter plan. If you try to connect Google Calendar on a plan without it, the card shows a locked button that names the feature and the Business plan, and it links to Billing. Full figures, including yearly prices, are on the pricing page.
Klugon's trial lasts 7 days. A card is needed to start, and you are charged at the end unless you cancel.
Limits of the Google Calendar connection
These are the limits worth knowing before you rely on the connection.
- One calendar. Each workspace connects one Google Calendar ID. If several staff members each keep their own Google Calendar, Klugon checks only the one you connected. You can share several people's calendars into one shared calendar on the Google side, but Klugon still sees just the calendar ID you pasted.
- Staff-level checks happen in Klugon, not Google. Klugon's own conflict check can be per staff member. The Google check is for the whole connected calendar, whichever staff member the customer asked for.
- The main slot finder doesn't look at Google. When the assistant lists open slots, it uses Klugon's own slot finder, which reads Klugon's bookings and rules only. Google is consulted when the assistant checks a specific time with
check_availability. In most conversations the assistant does that before confirming, but it is a decision the AI makes in the conversation, not a hard rule enforced on every booking. - Errors count as free. If Google can't be reached, or the key has been revoked, the check fails quietly and the time is treated as free. This is deliberate, so a broken connection doesn't stop all bookings, but it means a broken key can lead to a double booking. Keep the key and calendar sharing in place.
- Copies are optional. A booking is copied into Google only when the assistant asks for it in that call. Do not assume every booking will appear in Google.
- Changes in Google are not read back. Moving or deleting a Google event does not change Klugon's booking.
- Text channels only. No Google checks or copies on phone calls.
What Google Calendar AI booking doesn't do
To save you a support ticket later, here is what the connection does not do:
- It is not two-way sync. Klugon does not import your Google events, and Google changes are not reflected in Klugon.
- It does not guarantee that nothing will be double-booked. It lowers the risk when the assistant checks, and only for the calendar you connected.
- It does not send the customer a Google Calendar invitation or add them as a guest.
- It does not send confirmations or reminders by email or text. The customer's confirmation is the reply in the conversation, with a booking reference.
- It does not work on phone calls.
- It does not use "Sign in with Google". There is no OAuth button for Google Calendar in Klugon; the connection is the service account key you paste.
- It does not create Google Meet links.
- It does not connect several Google calendars at once.
If any of those is essential, Klugon's Bookings page plus a manual check each morning may be the safer workflow, or you can use Zapier to act on every booking event, whatever the channel.
A sample booking with Google Calendar connected
This is a sample conversation for a made-up physiotherapy clinic, Riverside Physio, to show the order of steps. It is not a transcript from a real customer.
Notice what happened: Google told Klugon only that 3.30 to 4.30 was busy. The assistant never saw the words "School pickup".
Practical tips for a reliable setup
A few habits make the connection far more dependable.
Pick the right calendar
Connect the calendar where your real availability lives. If you keep work in one calendar and personal life in another, consider which one should block customer bookings. Many owners create a dedicated calendar for "unavailable" blocks and connect that.
Block time in Klugon too
Because the main slot finder reads Klugon only, add holidays and closed dates in Klugon's booking settings as well as in Google. That way the slots the assistant offers in the first place are right, and the Google check is a second line of defence rather than the only one.
Check the connection monthly
Open your website chat once a month and ask for a slot you know is busy in Google. If the assistant offers it, something has broken: a revoked key, a changed sharing setting or a disabled API.
Keep Klugon as the morning list
Each morning, look at Klugon's Bookings page, not Google, for the day's appointments. That's the one list that includes every booking, from every channel, including phone calls. The guide to automating appointment booking has a fuller daily routine.
If you need every booking in Google
If your team works only from Google Calendar and you need every booking there, use Klugon's Zapier connection. Klugon sends a booking.created event to Zapier for every booking, including bookings taken on phone calls, and you can build a Zap that creates a Google Calendar event from it. That route also needs a Business plan or higher. It is a one-way push, so the same rule applies: changes made in Google later are not read back into Klugon.
How it compares with Outlook, Apple Calendar and Calendly
Klugon can also connect other calendars, and they behave similarly in most respects:
| Calendar | How you connect | What the assistant can do |
|---|---|---|
| Google Calendar | Service account key and calendar ID | Check busy times; copy, update and delete events through the calendar tools |
| Outlook | Microsoft sign-in | Check busy times; copy, update and delete events |
| Apple Calendar (iCloud) | Apple ID, app-specific password and calendar name | Check busy times; copy, update and delete events |
| Calendly | Personal access token | Check busy times; send the customer a single-use Calendly link |
Calendly is the odd one out: instead of copying a booking, the assistant can hand the customer a Calendly link so the booking is made in Calendly. That is covered on the Calendly AI receptionist page. All the connections Klugon offers are listed on the integrations page.
Frequently asked questions
Does Klugon sync with Google Calendar automatically?
Not in the sense most people mean. Klugon checks busy times in your connected Google Calendar when the assistant checks a specific slot, and it copies a booking into Google only when the assistant chooses to. Google changes are not read back. Treat it as a busy-time check plus optional copies, not as two-way sync.
Will Google Calendar events show up as bookings in Klugon?
No. Klugon asks Google for busy periods only. It never imports your Google events, their titles or their details, so they don't appear on the Bookings page.
Does the AI phone receptionist check Google Calendar during calls?
No. On phone calls the assistant uses Klugon's own slot finder and booking tool, which read Klugon's calendar only. The Google connection is used in website chat and messaging conversations.
Why is there no "Sign in with Google" button?
Klugon connects to Google Calendar with a service account key that you create in Google Cloud and paste into the dashboard. That avoids tying the connection to one person's login, but it does mean a few more setup steps.
Can I connect more than one Google Calendar?
Not at the moment. Each workspace connects one calendar ID. If you need several people's busy times, one option is to keep a shared calendar that holds everyone's blocks and connect that one.
What happens if my Google key stops working?
The busy-time check fails quietly and the time is treated as free, so bookings carry on but Google is no longer consulted. Copies into Google will also fail. Test the connection regularly by asking for a slot you know is busy.
Does the customer get a Google Calendar invite?
No. The event Klugon creates is on your calendar only. The customer gets a confirmation in the same conversation, with a booking reference, and nothing is sent by email or text.
Which plan do I need for Google Calendar AI booking?
A Klugon voice or social plan on the Business tier or above. It isn't part of the chat widget plans. Prices are on the pricing page.
Set up properly, the Google connection does one useful job: it lets Klugon's AI receptionist avoid the times you've already blocked in Google when it books customers in chat and messaging. Keep Klugon's own Bookings page as your diary of record, test the connection now and then, and it will quietly do that job in the background.