Read availability and calendars, and manage events through a named Google account.
Explore 9 workflow actions for Google Calendar, including account permissions and operation limits.
6 read actions3 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Check calendar availability
Read
Read busy periods for one calendar in a bounded time window.
An existing Google Calendar connection must reconnect to grant free/busy access. This returns busy periods only, not event details.
Create event
Write
Create one timed or all-day event in a selected calendar.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/calendar.events
Operation limits
Use start and end for a timed event, or startDate and endDate for an all-day event. An all-day end date is exclusive. Invitations depend on sendUpdates and the connected account's calendar permissions. This operation does not create a conference link.
A write is sent once. If Google's receipt is lost, the run remains uncertain and NodeHub does not repeat it automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Delete event
Write
Delete one event from a selected calendar.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/calendar.events
Operation limits
Guest notifications follow sendUpdates. Google's default applies when it is omitted.
A write is sent once. If Google's receipt is lost, the run remains uncertain and NodeHub does not repeat it automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Get event
Read
Read one event by its Calendar event ID.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/calendar.events
List calendars
Read
Read one page of calendars in the connected account's list.
Lists calendars visible to the connected account. It does not grant write access to every listed calendar.
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
List events
Read
Read one page of events in an explicit time window.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/calendar.events
Operation limits
The date window cannot exceed 366 days. Recurring events are expanded by default.
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
Review overlapping Google Calendar events
Read
The authorized user's primary calendar only, for the next selected number of days. Event IDs, busy intervals and own response status. No titles, descriptions, locations or addresses.
Read-only bounded report for the authorized user only. No writes, shared mailboxes or secondary calendars. A partial page is explicitly marked. Mail is unread, not proven unanswered. Overlap is not proven scheduling error.
Pagination: limited. Check the result for additional pages; a single action may not return every record.
Sync calendar changes
Read
Read a page of event changes, including cancellations, with a Google sync cursor.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/calendar.events
Operation limits
Use the next page token with the same sync token until Google returns a new sync token. HTTP 410 means the cursor expired and changes may have been missed.
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
Update event details
Write
Patch an event's details, schedule or complete guest list.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/calendar.events
Operation limits
Google charges three quota units for an event patch. This operation updates only the supplied fields. Change a complete timed pair or a complete all-day pair, never a mixed pair. An all-day end date is exclusive. Supplying attendees replaces the complete guest list; use an empty list to remove every guest. Guest notifications follow sendUpdates.
A write is sent once. If Google's receipt is lost, the run remains uncertain and NodeHub does not repeat it automatically.
A repeated request may repeat the external action. Review the previous result before retrying a write.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in Google Calendar. A saved workflow is not a completed provider action.
Scheduling · CONNECTION
