Google Calendar node

Create events in Google Calendar or list existing events in a time window. Title, attendees, and description can come from workflow data. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

8 min readUpdated September 10, 2026

What this node does

Create events in Google Calendar or list existing events in a time window. Title, attendees, and description can come from workflow data.

Use Google Calendar as a clearly defined step in an anymize workflow.

Processes one input.
Provides one output for following steps.
Runs as a regular step in the flow.

Set up the node

01Open a workflow and add Google Calendar from the node catalog.
02Select your google_byo connection. You can create it directly in the workflow if needed.
03Complete the required fields and map values from previous steps.
04Run the node with a small test record and inspect its output.
05Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

Create event
List events

Settings

Field	Meaning	Area
Action	Choices: Create event, List events	Standard
Calendar	Leave empty for your main calendar. For a different one: enter the calendar's email address.	Standard
Title	Configure this value in the node panel.	Standard
Description	Configure this value in the node panel.	Standard
Start	When does the event begin? Pick a date and time, or switch to variable for {{ … }} from a previous step.	Standard
End	When does the event end? Pick a date and time.	Standard
Attendees	Guests' email addresses, separate multiple with a comma.	Standard
From	Only show events from this point on. Pick a date and time.	Standard
To	Only show events up to this point. Pick a date and time.	Standard
Max hits	Configure this value in the node panel.	Standard
Run once per item	Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.	Standard
If one item fails	"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.	Standard
Pause between items (milliseconds)	Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).	Standard

Inputs and outputs

Input	Meaning	Type
Standard	Receives the complete result from the previous step.	JSON

Output	Meaning	Type
Standard	Makes the result available to the next step as JSON.	JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Kick-off event: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "summary": "Kick-off Meeting",
  "start": "2026-05-01T09:00:00+02:00",
  "end": "2026-05-01T10:00:00+02:00",
  "attendees": "alice@firma.de"
}

Access and security

This node uses a connected google_byo account. Review the requested permissions and grant only the required access.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

No output: inspect the latest run and confirm that the previous node returned the expected fields.
Empty variable: open the previous step output and use a field name from the real test data.
Connection rejected: reconnect the service and grant the permissions required by this step.
List processed once: enable per-item execution in advanced settings.