Skip to main content

Google Calendar

Connect Google Calendar to ORQO so that agents can list, create, update, and manage calendar events through MCP tools.

CategoryProductivity
CapabilitiesMCP tools only (no send/receive channel)
Adapter path/google_calendar
Auth methodOAuth 2.0 (shared Google credential)
info

Google Calendar is an MCP-only integration. It provides tools for agents to manage calendar events programmatically — listing upcoming events, scheduling meetings, updating details, and checking availability. It does not support inbound event notifications through Chief of Staff or channels.

Prerequisites

  • A Google account with Google Calendar access
  • A Google Cloud project with the Google Calendar API enabled
  • OAuth 2.0 credentials (client ID and client secret)
  • Access to the ORQO Settings area

Setup

1. Set Up Google Cloud Credentials

  1. Go to the Google Cloud Console.
  2. Create a project (or select an existing one).
  3. Enable the Google Calendar API under APIs & Services > Library.
  4. Navigate to APIs & Services > Credentials and create OAuth 2.0 Client ID credentials (or reuse credentials from another Google integration).
  5. Set the redirect URI to the OAuth Callback URL shown on the app's detail card in ORQO.
  6. Note the client ID and client secret.

2. Install the Google Calendar App in ORQO

  1. Navigate to Settings > Integrations in ORQO.
  2. Switch to the Catalog tab and find Google Calendar.
  3. Click the card to view details, then click Install.

Google Calendar uses the shared Google OAuth credential:

CredentialTypeDescription
GOOGLE_OAUTH2oauth2OAuth 2.0 credentials (client ID, client secret, tokens)

Create the credential in Settings > Credentials with your Google Cloud client ID and client secret, then assign it to the Calendar app. If you already have a GOOGLE_OAUTH2 credential from another Google integration (Drive, Gmail), assign that same credential — no need to create a new one.

Shared Google credential

For a single Google account, all Google integrations (Drive, Gmail, Calendar) can share the same GOOGLE_OAUTH2 credential — install any of them first and the others will reuse it. To connect a different Google account, install Google Calendar again as a separate, named instance with its own credential (see Connect Multiple Calendars below).

4. Authorize via OAuth

  1. Click Connect with OAuth on the Google Calendar app card.
  2. Google's consent screen shows the requested Calendar permissions.
  3. Approve access. ORQO stores the tokens and refreshes them automatically.

Because all Google integrations use incremental authorization, authorizing Calendar adds the Calendar scope to your existing Google token — it does not revoke Drive or Gmail access.

5. Verify the Connection

Click Verify on the Google Calendar app card. This tests the connection and discovers the available MCP tools.

Connect Multiple Calendars

You can install Google Calendar more than once to connect several Google accounts to the same organization. When you install it again, give the new install a distinct name (such as "Calendar – Ops" or "Personal Calendar") so you can tell the accounts apart.

Each install gets its own credential and is authorized independently with Connect with OAuth — sign in to the account you want for that install. In a workflow, different agents can use different calendars; their tools are kept separate automatically.

See Connect multiple accounts of the same service for the full walkthrough.

(To work with multiple calendars belonging to a single account, you don't need a second install — pass a calendar_id to the tools, as described under Platform-Specific Behavior.)

Available Tools

ToolDescription
google_calendar_list_eventsList upcoming events (filter by date range, calendar, or search query)
google_calendar_get_eventGet full event details including attendees and conference links
google_calendar_create_eventCreate a new event with title, time, attendees, location, and description
google_calendar_update_eventUpdate an existing event (only provided fields are changed)
google_calendar_delete_eventDelete a calendar event
google_calendar_list_calendarsList all calendars accessible to the user

These tools are discovered automatically when the app is verified and can be assigned to agents via Skills.

Date and Time Formats

The Calendar tools accept ISO 8601 date-time strings:

FormatExampleUse
Date + time + timezone2025-01-15T10:00:00-07:00Timed events
Date + time in UTC2025-01-15T17:00:00ZTimed events (UTC)
Date only2025-01-15All-day events

Platform-Specific Behavior

  • OAuth 2.0 with incremental scopes — Calendar uses the calendar scope. When authorized alongside Google Drive or Gmail, scopes are merged into a single token.
  • Primary calendar default — All tools default to the user's primary calendar. Pass a calendar_id (from google_calendar_list_calendars) to work with other calendars.
  • Recurring eventsgoogle_calendar_list_events expands recurring events into individual instances (singleEvents: true), so each occurrence appears separately in the results.
  • Attendee managementgoogle_calendar_create_event and google_calendar_update_event accept comma-separated email addresses for attendees. Google sends invitation emails automatically.

What's Next

  • Google Drive — file access using the same Google credential
  • Gmail — email management using the same Google credential
  • Create a Skill — bundle Calendar tools for agents
  • Set Up an App — general app installation guide