Overview

The Google Calendar connector for Gemini Enterprise lets you access your Google Calendar data and interact with calendar events and calendars.

Supported Google Calendar versions

The Google Calendar data store supports Google Calendar version v3 and later.

Supported actions

When the Google Calendar data store is enabled, end users can use natural language commands in Gemini Enterprise to perform the following actions.

Action Description
Create Calendar Event Creates an event in your calendar.
Update Calendar Event Updates the metadata for an event in your primary calendar.

Required scopes

The following table lists the minimum scopes required for Google Calendar search and actions:

Connection mode Scope Purpose
Federated search https://www.googleapis.com/auth/calendar.readonly Minimum permission for federated search and read-only actions.
Federated search and Actions https://www.googleapis.com/auth/calendar.readonly Required for read access when performing write actions like creating events.
https://www.googleapis.com/auth/calendar.events Required to create calendar events.
https://www.googleapis.com/auth/calendar.calendars Required to update calendar event metadata.

For information on how to configure these scopes, see Add scopes.

Limitations

  • The Google Calendar data store is only supported in the EU, US, and Global locations.

  • When creating a new application or adding a data store to an existing application, we recommend that you add a data store of a single connector type. For example, don't associate two Google Calendar datastores with actions in the same application.

  • If you use security controls, be aware of their limitations related to data in Google Calendar, as discussed in the following table:

    Security control Note the following
    Data Residency (DRZ) Gemini Enterprise only guarantees data residency in Google Cloud. For information about data residency and Google Calendar, see Google Workspace compliance guidance and documentation, including Data regions for Google Workspace. Also review examples like Choose the region where data is stored and Digital sovereignty.
    Customer-managed encryption keys (CMEK) Your keys only encrypt data within Google Cloud. Cloud Key Management Service controls don't apply to data stored in Google Calendar.
    Access Transparency Access Transparency logs actions taken by Google personnel on the Google Cloud project. You'll also need to review the Access Transparency logs created by Google Workspace. For more information, see Access Transparency log events in the Google Workspace Admin Help documentation.

What's next