Calendar

Google integration · 4 node(s).

00Overview

Google Calendar event management

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Calendar

Add your credentials as a Flomation environment secret, then pick them in each node. The connection fields are:

Pick an Environment on your flow (Flow Settings → Environment) so the secret resolves. Secret fields never show the value — they reference ${secrets.your_secret}.

02Create

Calendar Create Event

google/calendar/create · Action

Create a new event on a connected Google Calendar. Specify the account (email or label like 'Work'/'Personal'), date, time, title, and optional attendees/location.

Field	Type		Details
Event title	`string`	Required
Date (YYYY-MM-DD, 'today', 'tomorrow', or day name)	`string`	Required
Start time (HH:MM, 24h format)	`string`	Required
End time (HH:MM, 24h format)	`string`	Required
Event description or notes	`string`
Attendees (comma-separated email addresses)	`string`
Event location	`string`
Account (email, label like 'Work'/'Personal', or empty for primary)	`string`
Google OAuth Credential (optional, overrides user tokens)	`credential`		${credentials.GOOGLE_CALENDAR}

Returns: tool_result, event_id, event_link, success, error

03Delete

Calendar Delete Event

google/calendar/delete · Action

Delete an event from Google Calendar. Requires the event_id from a previous calendar_read. This permanently removes the event.

Field	Type		Details
Event ID (from calendar_read results)	`string`	Required
Account the event is on (email or label)	`string`
Google OAuth Credential (optional, overrides user tokens)	`credential`		${credentials.GOOGLE_CALENDAR}

Returns: tool_result, success, error

04Read

Calendar Read

google/calendar/read · Action

Read events, check availability, or find free slots across all connected Google calendars

Field	Type		Details
Query Type	`string`	Required	choices: List events, Check availability, Find free slots
Start Date (YYYY-MM-DD or 'today', 'tomorrow')	`string`	Required	today
End Date (YYYY-MM-DD, defaults to date_from)	`string`
Start Time (HH:MM, for availability check)	`string`		14:00
End Time (HH:MM, for availability check)	`string`		15:00
Slot Duration (minutes, for free slot search)	`integer`		60
Account filter (email, label like 'Work', or empty for all)	`string`
Google OAuth Credential (optional, overrides user tokens)	`credential`		${credentials.GOOGLE_CALENDAR}

Returns: tool_result, events, is_free, free_slots, success, error

05Update

Calendar Update Event

google/calendar/update · Action

Update an existing Google Calendar event. Requires the event_id from a previous calendar_read. Only the fields you provide will be changed; others remain untouched.

Field	Type		Details
Event ID (from calendar_read results)	`string`	Required
New title (leave empty to keep current)	`string`
New date (YYYY-MM-DD, leave empty to keep current)	`string`
New start time (HH:MM, leave empty to keep current)	`string`
New end time (HH:MM, leave empty to keep current)	`string`
New description	`string`
New location	`string`
Account the event is on (email or label)	`string`
For recurring events: 'this_instance' (default), 'all_events' (change the entire series), or 'this_and_following' (this and all future instances)	`string`		choices: This instance only, All events in series, This and following
Google OAuth Credential (optional, overrides user tokens)	`credential`		${credentials.GOOGLE_CALENDAR}

Returns: tool_result, success, error

06Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

Deleting an event is permanent — there is no undo, so verify the event before wiring a delete step into an automatic flow.
Updating or deleting an event needs the event_id produced by an earlier read step, so always chain a read ahead of those actions rather than deleting straight from a trigger.
Adding attendees to an event can automatically email them a calendar invitation, so test the create and update steps with your own address before pointing them at real contacts.
Acting on a recurring event by its event_id affects the whole series rather than a single occurrence, so target the specific instance when you only mean to change one date.