Short answer: Drop the "Google Calendar → Quick Add 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 Text text | string | Required | Natural language description of the event including date, time, and title |
Send Notifications sendUpdates | options | Optional | Whether to send notifications about the event |
{"calendar_id": "primary","text": "e.g. Lunch with Sarah tomorrow at 12:30pm at The Italian Place","sendUpdates": "{{trigger.sendUpdates}}"}
{"id": "evt789xyz","end": {"dateTime": "2025-01-21T13:30:00-05:00","timeZone": "America/New_York"},"start": {"dateTime": "2025-01-21T12:30:00-05:00","timeZone": "America/New_York"},"status": "confirmed","summary": "Lunch with Sarah","htmlLink": "https://calendar.google.com/calendar/event?eid=evt789xyz","location": "The Italian Place"}
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.