Google Calendar Action
Reads and writes Google Calendar from a flow. Nine operations — create an event, move it, invite people, look for a free slot, cancel — so a booking that arrives by webhook can land on a calendar without anyone retyping it.
Setup
A Google credential with the calendar scope. The calendar itself is picked per operation; the account's primary calendar is the default.
Mode — action or AI toolkit
The Mode selector decides who drives the node. In Action mode you pick one operation and fill its fields, and the node does that every time it runs. In AI toolkit mode the operations become tools an AI Node can call, and the model chooses which one and with what arguments.
Operations
The Operation dropdown decides what the node does and which fields appear under it. These are the exact values the API validates against:
| Value | In the dropdown | What it does |
|---|---|---|
| createEvent | Create Event | Create a new calendar event |
| updateEvent | Update Event | Update an existing event by ID |
| deleteEvent | Delete Event | Delete an event by ID |
| listEvents | List Events | List events in a date range |
| getEvent | Get Event | Get a single event by ID |
| listCalendars | List Calendars | List the calendars you can write to (iterable output) |
| findFreeSlots | Find Free Slots | Find open windows in a date range (iterable output) |
| proposeEvent | Propose Event (tentative) | Create a tentative event — no invites sent |
| confirmEvent | Confirm Proposed Event | Promote a tentative event and send invites |
Gotchas
- Times need a timezone. An event created without one lands in the calendar's default zone, which is rarely the customer's — pass an explicit offset or an IANA zone.
- Inviting an attendee sends mail from the connected account. That is Google's behaviour, and it surprises people the first time a test run emails a real customer.
- An all-day event uses dates, not timestamps. Mixing the two is the usual cause of an event that lands one day off.
- Cancelling is not deleting. A cancelled event stays visible to attendees with a strikethrough; deleting removes it from their calendars too.