Google Calendar
Integration · Workspace and scheduling
Google Calendar and AI agents: booking against real availability.
Through the Google Calendar API, an agent can check free and busy time, create, move and cancel events, and invite attendees. That is enough to book appointments from a conversation, as long as you write down the booking rules the calendar itself does not know.
What can an agent do in Google Calendar?
- Check availability across one or several calendars, for example every practitioner in a clinic, before offering times.
- Create, move and cancel events, with a description, location and attendees, and send Google’s own invitations if you want them.
- Add a video meeting link to events, where your Workspace settings allow it.
- Watch for changes, so the agent knows when a person moves or deletes an event by hand.
- Read the day ahead to send reminders or prepare a daily run sheet.
These cover the core of appointment booking and the booking half of an AI receptionist.
For example, a hypothetical dental practice with three dentists and a hygienist could keep one calendar per person. A patient asks on WhatsApp for a cleaning next week; the agent checks only the hygienist’s calendar, offers two times that respect the practice’s buffers, books the chosen one and sends a confirmation.
What does the calendar not know?
A calendar knows when someone is busy. It does not know your business rules, and that is where most booking bugs come from. Write these down before the build:
| Rule | Example question to answer |
|---|---|
| Services and durations | Does a first consultation take longer than a follow-up? |
| Who does what | Which staff can take which services, and on which days? |
| Buffers and travel | Do you need gaps between appointments, or travel time between sites? |
| Lead time and horizon | How soon can someone book, and how far ahead? |
| Changes and cancellations | Until when can a customer move a booking without a person approving it? |
| Holds | Should the agent hold a slot for a few minutes while the customer confirms? |
Keep these rules somewhere your team can edit, such as a settings table, rather than inside the agent’s instructions.
Rules written in code or a settings table are applied the same way every time. Rules written only in an AI model’s instructions can be misread or talked around by a determined customer. Use the model to understand what the person wants, and ordinary code to decide which slots are allowed.
What goes wrong with calendar integrations?
- Double bookings. Availability can change between offering a time and booking it. Check again immediately before creating the event.
- Time zones and daylight saving. Store and compare times with their time zone. Irish clocks change twice a year, and customers abroad see times differently.
- Personal events on work calendars. Decide whether the agent sees event details or only busy and free time. Free/busy is usually enough and shares less.
- Quotas. The API has usage limits. A busy booking agent should cache sensibly and avoid polling every calendar every few seconds.
Before you connect Google Calendar: a checklist.
Connecting Google Calendar safely
0 of 8 done
How is access set up?
For a team, the usual approach is a service account that each relevant calendar is shared with, or one authorised by your Google Workspace admin for the calendar scope only. Give it permission to make changes only on calendars it books into, and free/busy only on the rest. Events the agent creates then show up in your team’s calendars like any other.
Is a booking page enough?
If customers are happy to pick a slot from a link, use a booking page: Google Calendar’s own, or a tool such as Calendly. A custom agent is worth it when bookings arrive in conversation (WhatsApp, phone, email), when the rules are too specific for a booking tool, or when the booking has to update other systems such as a CRM, a payment or a follow-up sequence.
How do reminders fit in, and what should you measure?
Booking is half the job. The other half is making sure people turn up. Because the agent can read the day ahead, it can send reminders through the channel the customer used, offer to move the appointment if they cannot make it, and free the slot for someone else when they cancel.
On WhatsApp, a reminder sent outside the customer service window needs an approved template, so plan the wording early. See the WhatsApp page.
- Bookings completed without a person, and the share that needed a handoff.
- Time from enquiry to confirmed booking, compared with before.
- No-shows and late cancellations, before and after reminders started.
- Errors: double bookings, wrong durations or wrong staff, each one reviewed and fixed at the rule level.
Common questions
Can the agent book into several staff calendars?
Yes. It checks each relevant calendar’s availability and books into the right one according to your rules, for example by service, location or who the customer saw last time. Each calendar needs to be shared with the agent’s account, or reachable through admin-approved access, with permission to make changes.
What if a staff member moves an appointment by hand?
The agent should watch for changes and treat the calendar as the source of truth. If an appointment moves, it can tell the customer, or flag it for a person if the new time breaks a rule. Without change notifications, it will keep working from out-of-date information.
Does this work with Outlook calendars too?
The same pattern works with Microsoft 365 calendars through Microsoft Graph. The access model is different and is approved in Microsoft Entra rather than Google’s admin console. If your team uses both, pick one calendar as the source of truth for bookings to avoid conflicts between them.
Can customers book without creating an account?
Yes. The agent collects the details it needs in conversation and creates the event itself, so the customer does not need a Google account. Send confirmations through the channel they used, such as WhatsApp or email, rather than relying only on a calendar invitation.
Bring us the task.
Tell us what happens today, which tools are involved and where it goes wrong. On a free 30-minute review, we’ll work out whether an agent, an automation or neither is the right fix, and what a sensible first release would be.
Start a project.

Book a call or send us a message. We read everything.
tash@neu.ie
Working with teams in Ireland and worldwide.
Free 30-minute AI review.