Google Calendar

How Dispatch reads availability and creates, updates, and responds to events on your Google Calendar.

To connect Google Calendar, open the in-app Connections settings.

Google Calendar is one of two calendar backends Dispatch supports (the other is Outlook Calendar). Once connected, the agent reads your free/busy directly and creates events that show up on your real calendar.

OAuth scopes

Dispatch requests the Google Calendar API scopes it needs and no more. The in-app connect screen shows the current scope request before you authorize.

Read capabilities

  • List events on any connected calendar within a date range.
  • Search events by attendee, title, or text.
  • Free/busy queries across one or more calendars.
  • Read attendee responses and event metadata (location, conference data, attachments metadata).

Write capabilities

All writes carry the external-write risk annotation and pass through the permission gate.

  • Create events (with attendees, conferencing, reminders, time zone).
  • Update events (time, attendees, location, description).
  • Cancel events.
  • Respond to invitations (accept, decline, tentative).
  • Quick-add events from natural-language strings ("lunch with Sarah Thursday").

What automations can use

Three event-driven triggers fire off the calendar:

  • Event Added. A new meeting was added to the user's calendar via incremental sync.
  • Meeting Prep. Fires shortly before a scheduled meeting so the agent can brief.
  • Transcript Received. Fires when a meeting transcript becomes available, including transcripts produced by the meeting notetaker.

Scheduled actions can also read or modify calendars on a cron-like cadence (for example, a morning briefing that summarizes today's events). Triggers on event changes or RSVP changes are not currently exposed.

Limits and behavior

  • Multiple calendars per account. The agent can read and write across all calendars you have access to on a connected account.
  • Multi-account. A user can connect multiple Google accounts; the agent picks the right one when explicit, asks otherwise.
  • Conference data. When creating events the agent can add a Google Meet conference automatically.
  • No automatic time-zone inference. The agent uses the calendar's configured time zone by default; explicit time-zone language in your request overrides.

On this page