Connecting Google Calendar lets your AI agent book appointments directly into your calendar during live calls — no manual entry, no follow-up required. This article covers how to connect, configure, and get the most from the integration.
What the integration does
Once connected, your agent can do three things automatically during a call:
Connecting Google Calendar
The integration uses OAuth — a secure one-click authorisation flow. VoiceForge Pro never stores your Google password.
- Open the Integrations tabGo to Agents → Edit → Integrations and click Connect Google Calendar.
- Authorise accessA Google OAuth window opens. Sign in and grant VoiceForge Pro permission to read/write calendar events.
- Select your calendarIf your Google account has multiple calendars, select which one bookings should be created in.
- Configure booking settingsSet your working hours, appointment duration, booking lead time, and buffer between appointments.
- Sync your agentClick Sync to Voice Agent. From the next call, your agent will check availability and offer real bookings.
Booking configuration settings
| Setting | What it controls | Example |
|---|---|---|
| Working hours | Days and hours when bookings can be made. The agent won't offer slots outside these hours. | Mon–Fri, 8am–6pm |
| Appointment duration | How long each slot is. | 60 minutes |
| Booking lead time | Minimum notice required. No slots sooner than this. | 2 hours |
| Buffer time | Gap left between appointments for travel or wrap-up. | 15 minutes |
| Max advance booking | How far ahead the agent can book. | 4 weeks |
| Event status | Whether bookings are Confirmed or Tentative. | Confirmed (default) |
What callers experience
With Google Calendar connected, a booking call sounds like this:
Revoking access
To disconnect, go to Agents → Edit → Integrations and click Disconnect next to Google Calendar. You can also revoke at myaccount.google.com/permissions. Revoking stops future bookings but does not delete events already created.
Note for agencies
Each agent connects to a separate Google Calendar. When deploying for clients, the client should authorise their own Google account — not yours. Their bookings go into their calendar; you have no access to their calendar data. Walk them through the OAuth flow during onboarding.