Docs / Workflows / Integrations / Google Calendar
Google Calendar
Read availability and create, change or answer events in Google Calendar.
What you can do
Each Google Calendar integration’s page in OAIZ shows these uses, with its events and its read and write actions, under What you can do with Google Calendar.
- Bookings
- Create a calendar event when a customer books a call.
- Free and busy times
- Check free and busy times before suggesting a meeting.
- Daily agenda
- Post tomorrow’s meetings to your team every evening.
Connection scope
A connection reaches calendars available to its Google account. Calendar IDs select the calendar, and event IDs select the item within it. List Calendars reports each calendar’s access role. Writes require a writable calendar.
Connecting
Google Calendar connections must be enabled for your OAIZ organization before you can connect or reauthorize this service. Choose Google Calendar in OAIZ and authorize the Google account whose resources the workflows should use. If this service is being added to an existing Google connection, use the same Google account.
Google permissions
OAuth scopes are the permissions OAIZ requests from Google. Each connection asks for account identity and the permissions for its selected service. Adding another Google service requests its additional permissions on the same account. Google’s consent screen shows the exact access before you approve.
openid
https://www.googleapis.com/auth/userinfo.email
https://www.googleapis.com/auth/calendar.events
https://www.googleapis.com/auth/calendar.calendarlist.readonly
https://www.googleapis.com/auth/calendar.events.freebusy- openid
- Identify the Google account that owns the shared connection.
- userinfo.email
- Show the connected Google account’s email address in OAIZ.
- calendar.events
- Read and manage calendar events, respond to invitations, and watch event changes that start workflows.
- calendar.calendarlist.readonly
- List the account’s calendars and find readable calendars to watch, including calendars added later.
- calendar.events.freebusy
- Read availability when scheduling or evaluating an event.
Read actions
- List Calendars
- List calendars available to the connected account with exact IDs and access roles.
- Get Free Busy
- Read busy intervals for 1 to 50 calendars within a time window.
- List Events
- List one page of events from a calendar, with optional time, search, recurrence-expansion, and ordering filters.
- Get Event
- Get one event and its current etag from a calendar.
Write actions
- Create Event
- Create a timed, all-day, or recurring event on a writable calendar.
- Update Event
- Change selected event fields. Supplied attendee and recurrence lists replace the existing lists. An etag can guard against conflicting edits.
- Delete Event
- Delete an event, optionally checking its etag before making the change.
- Respond To Event
- Accept, tentatively accept or decline an invitation by changing the calendar owner’s attendee response.
Events
Event Created and Event Updated describe items observed on watched calendars. Event Cancelled covers cancellation or removal, including deleted events and removed attendees. Its payload contains only the fields Google returns, sometimes just the event ID and cancelled state.
Google data use and removal
The business customer controls workflows using the connected account. Google data can become input to an action that uses AI, such as LLM call, Agent or Decision. OAIZ sends that input to the LLM provider or TypeSafe AI decision engine used for the action to produce the requested output. OAIZ does not use Google data to train, fine-tune or improve AI models. OAIZ does not sell Google data or share it for advertising.
OAIZ stores connection credentials while services are connected. Google data can also be stored in workflow events, execution history and files. Removing a service does not erase these retained records. The privacy policy and Data Processing Agreement explain storage, sharing, retention and deletion. Contact the business customer or support@oaiz.io to request deletion of retained data.
Removing one Google service stops its OAIZ actions and subscriptions. Other services on the same account keep the shared connection and accumulated Google permissions. Removing the final service deletes the stored credential and requests revocation at Google. The disconnect result reports whether Google confirmed revocation.
OAIZ’s use and transfer of Google API data follows Google’s Limited Use requirements. For Gmail, Google Calendar and Google Drive, OAIZ also follows the additional requirements of the Google Workspace API User Data and Developer Policy described in the privacy policy.