Short answer: Drop the "Google Calendar → List Calendars" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Minimum Access Role minAccessRole | options | Optional | Filter calendars by the user's minimum access role |
Show Hidden Calendars showHidden | options | Optional | Include hidden calendars in the list |
{"minAccessRole": "{{trigger.minAccessRole}}","showHidden": "{{trigger.showHidden}}"}
{"items": [{"id": "primary","primary": true,"summary": "user@example.com","timeZone": "America/New_York","accessRole": "owner","backgroundColor": "#4285f4"},{"id": "en.usa#holiday@group.v.calendar.google.com","summary": "Holidays in United States","accessRole": "reader","backgroundColor": "#16a765"},{"id": "team-calendar@group.calendar.google.com","summary": "Team Calendar","timeZone": "America/New_York","accessRole": "writer","backgroundColor": "#f83a22"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.