The Google Calendar connector for Gemini Enterprise lets you search and perform actions on your 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 event | Creates a new Google Calendar event. |
| Update event | Updates an existing Google Calendar event. |
| Delete event | Deletes an existing Google Calendar event. |
| Get event | Fetches a Google Calendar event by ID. |
| Respond to event | Responds to a Google Calendar event invitation. |
| List events | Lists events from a Google Calendar. |
| Search events | Searches for Google Calendar events matching a query. |
| List calendars | Lists calendars in the user's Google Calendar account. |
| Suggest time | Suggests a meeting time based on attendees' free/busy data. |
Required scopes
The Google-managed OAuth app requests the following OAuth scopes. Users grant these scopes when they authorize the connector:
| Scope | Purpose |
|---|---|
https://www.googleapis.com/auth/calendar.calendarlist.readonly |
List calendars in the user's Google Calendar account. |
https://www.googleapis.com/auth/calendar.events.readonly |
Read and search Google Calendar events. |
https://www.googleapis.com/auth/calendar.readonly |
Read Google Calendar metadata and event attachments. |
https://www.googleapis.com/auth/calendar.events |
Create, update, delete, and respond to Google Calendar events. |
https://www.googleapis.com/auth/calendar.events.freebusy |
Query attendees' free/busy data to suggest meeting times. |
https://www.googleapis.com/auth/calendar.freebusy |
Query free/busy information for a calendar. |
https://www.googleapis.com/auth/calendar |
Perform write operations on Google Calendar data. |
Limitations
- The Google Calendar data store is supported only in the
global,us, andeulocations.
- When creating a new app or adding a data store to an existing one, it's recommended to associate only one data store with actions belonging to a single connector type.
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
- To create and configure a connector with Google Calendar, see Set up a Google Calendar connector.