Short answer: Drop the "Google Calendar → List Events" 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 |
|---|---|---|---|
Calendar ID calendar_id | string | Required | Calendar ID. e.g. "primary" |
From Date timeMin | string | Optional | Show events after this date (ISO 8601) |
To Date timeMax | string | Optional | Show events before this date |
Max Results maxResults | string | Optional | Max Results. e.g. "10" |
Search Query q | string | Optional | Search Query. Example: standup |
{"calendar_id": "primary","timeMin": "e.g. 2025-01-15T00:00:00Z","timeMax": "e.g. 2025-02-15T00:00:00Z","maxResults": "10","q": "e.g. standup"}
{"items": [{"id": "evt123","end": {"dateTime": "2025-01-20T10:30:00-05:00"},"start": {"dateTime": "2025-01-20T10:00:00-05:00"},"summary": "Team Standup"}]}
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.