Google Calendar

Manage calendars, events, and scheduling via the Google Calendar API.

Detail	Value
Category	Scheduling
Base URL	https://www.googleapis.com/calendar/v3
Authentication	OAuth2
Endpoints	6
Connector key	google-calendar

Using Google Calendar in a workflow

1. Go to Connections and click New Connection.
2. Pick Google Calendar from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /calendars/{calendarId}/events	List calendar events
POST /calendars/{calendarId}/events	Create a calendar event
GET /calendars/{calendarId}/events/{eventId}	Get an event
DELETE /calendars/{calendarId}/events/{eventId}	Delete an event
GET /users/me/calendarList	List user calendars
POST /freeBusy	Find free/busy times

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /calendars/{calendarId}/events

List calendar events

Detail	Value
Operation ID	scheduling.listEvents
Method	GET
Path	/calendars/{calendarId}/events

Parameters

Name	Location	Type	Required
calendarId	path	string	Yes
timeMin	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Calendar connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.listEvents.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Calendar API reference.

POST /calendars/{calendarId}/events

Create a calendar event

Detail	Value
Operation ID	scheduling.createEvent
Method	POST
Path	/calendars/{calendarId}/events

Parameters

Name	Location	Type	Required
calendarId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Calendar connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.createEvent.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Calendar API reference.

GET /calendars/{calendarId}/events/{eventId}

Get an event

Detail	Value
Operation ID	scheduling.getEvent
Method	GET
Path	/calendars/{calendarId}/events/{eventId}

Parameters

Name	Location	Type	Required
calendarId	path	string	Yes
eventId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Calendar connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.getEvent.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Calendar API reference.

DELETE /calendars/{calendarId}/events/{eventId}

Delete an event

Detail	Value
Operation ID	scheduling.deleteEvent
Method	DELETE
Path	/calendars/{calendarId}/events/{eventId}

Parameters

Name	Location	Type	Required
calendarId	path	string	Yes
eventId	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Calendar connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.deleteEvent.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Calendar API reference.

GET /users/me/calendarList

List user calendars

Detail	Value
Operation ID	scheduling.listCalendars
Method	GET
Path	/users/me/calendarList

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Calendar connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.listCalendars.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Calendar API reference.

POST /freeBusy

Find free/busy times

Detail	Value
Operation ID	scheduling.queryFreeBusy
Method	POST
Path	/freeBusy

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Calendar connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.queryFreeBusy.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Calendar API reference.