Google Calendar

Google Calendar (google_calendar) is an OAuth integration whose nine tools Talqing runs directly against the Calendar REST API. Approval, tools_namespace, GET /v1/integrations/{integration_id}/mcp-tools and mcps attachment work as for any MCP server.

Connecting

Dashboard only: Integrations → Add integration → Google Calendar → approve as the account whose calendars the agent acts on → approve the tools it needs (an agent that only reads should not hold delete_event). The integration is named Google Calendar - <email>.

Scope	Used by
`openid`, `email`, `profile`	The account identity shown in the dashboard
`calendar.calendarlist.readonly`	`list_calendars`
`calendar.events.readonly`	`list_events`, `search_events`, `get_event`
`calendar.events.freebusy`	`suggest_time`
`calendar.events.owned`	`create_event`, `update_event`, `delete_event`, `respond_to_event`

Writes work only on calendars the connected account owns, not calendars shared with it. The model gets an error pointing it at list_calendars (which reports accessRole) and may book on a different calendar it owns. To write to a shared calendar, connect the account that owns it.

The nine tools

With the default namespace the model sees google_calendar_<tool>; approve the bare names.

Tool	What it does
`list_calendars`	Every calendar the account can see, with `accessRole`
`list_events`	Events on one calendar: optional time range, `fullText` match, type filter, ordering. Recurring events expanded into occurrences
`search_events`	Keyword search across up to 20 of the account’s calendars, 30 days back to 365 days ahead, sorted by start. Each hit names its calendar
`get_event`	One event by id
`create_event`	Create an event: title, start, end, attendees, location, description, reminders, availability
`update_event`	Change an event; omitted arguments are kept
`delete_event`	Delete an event
`respond_to_event`	Set the account’s own RSVP (accepted, declined, tentative)
`suggest_time`	Free periods inside a window when every listed attendee (max 50) is free

calendarId is optional everywhere and defaults to the primary calendar.

Rules that decide whether a booking is right

Timestamps need an offset. startTime must look like 2026-04-30T10:00:00+05:30, or the call must set timeZone; otherwise it is refused.
All-day end dates are exclusive. A one-day event on 2026-04-30 ends 2026-05-01.
Guests are notified by default when the event has attendees, unless the model opts out.
An event id from list_events or search_events addresses one occurrence of a recurring series, not the series.
suggest_time returns whole free periods, not slots; durationMinutes (default 30) is the shortest period returned. preferences.startHour/endHour are applied per local day in timeZone (or the primary calendar’s zone), so working hours stay correct across DST.
unreadableCalendars means unknown, not free. Attendees whose calendars Google will not share (usually outside the organisation) are listed there. Include the caller’s own address in suggest_time.
Deleting an already-deleted event returns That event has already been deleted.
Rate limits and transient errors are retried, up to three attempts with short backoff.

Prompting an agent to book

Set the agent’s timezone and put the date in the prompt — Today is {{system_vars.date}} — so “next Tuesday” resolves. Using {{system_vars.date}} without timezone is a save error. See variables.
Name the fields to collect before calling a tool (name, reason, day and time).
On voice, have the agent say a short line (“let me check the calendar”) before each call.
Have it read back what the tool returned, and never confirm without a successful create_event.

Today is {{system_vars.date}}. All times are Asia/Kolkata; every time you send to
a calendar tool carries the +05:30 offset, e.g. 2026-05-04T15:00:00+05:30.

Before booking, collect the patient's full name, the treatment and a preferred
day. Say "let me check the calendar", then call google_calendar_suggest_time for
that day, 09:00 to 18:00, and offer at most two times. Anyone in
unreadableCalendars is unknown, not free.

Book with google_calendar_create_event titled "<treatment> - <patient name>".
Read back the day, time and treatment from the result. If it failed, say so and
offer a callback.

Appointment booking

The end-to-end booking agent.

MCP servers

Attaching, approving and namespacing.

Get started

Build

Guides

Google Calendar

Connecting

The nine tools

Rules that decide whether a booking is right

Prompting an agent to book

Next

Appointment booking

MCP servers

​Connecting

​The nine tools

​Rules that decide whether a booking is right

​Prompting an agent to book

​Next

Appointment booking

MCP servers

Connecting

The nine tools

Rules that decide whether a booking is right

Prompting an agent to book

Next