Short answer: Drop the "Google Calendar → Update Event" 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 | Use 'primary' for the user's main calendar, or a specific calendar ID |
Event ID event_id | string | Required | The unique identifier of the event to update |
Event Title summary | string | Optional | Event Title. Example: Updated Team Standup |
Description description | string | Optional | Description. Example: Updated meeting agenda |
Start Date/Time start_dateTime | string | Optional | ISO 8601 format with timezone |
End Date/Time end_dateTime | string | Optional | ISO 8601 format with timezone |
Location location | string | Optional | Location. Example: Conference Room B |
Send Notifications sendUpdates | options | Optional | Whether to send update notifications to attendees |
{"calendar_id": "primary","event_id": "e.g. abc123def456","summary": "e.g. Updated Team Standup","description": "e.g. Updated meeting agenda","start_dateTime": "e.g. 2025-01-20T10:00:00-05:00"}
{"id": "abc123def456","end": {"dateTime": "2025-01-20T11:00:00-05:00"},"start": {"dateTime": "2025-01-20T10:00:00-05:00"},"status": "confirmed","summary": "Updated Team Standup","updated": "2025-01-18T15:30:00.000Z","htmlLink": "https://calendar.google.com/calendar/event?eid=abc123","location": "Conference Room B"}
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.