Calendly

Manage scheduling, events, invitees, and availability via Calendly.

Detail	Value
Category	Scheduling
Base URL	https://api.calendly.com
Authentication	Bearer Token
Endpoints	6
Connector key	calendly

Using Calendly in a workflow

1. Go to Connections and click New Connection.
2. Pick Calendly 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 /users/me	Get current user
GET /event_types	List event types
GET /scheduled_events	List scheduled events
GET /scheduled_events/{eventUuid}	Get a scheduled event
GET /scheduled_events/{eventUuid}/invitees	List event invitees
POST /scheduled_events/{eventUuid}/cancellation	Cancel an event

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

GET /users/me

Get current user

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

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Calendly connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.getMe.
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 Calendly API reference.

GET /event_types

List event types

Detail	Value
Operation ID	scheduling.listEventTypes
Method	GET
Path	/event_types

Parameters

Name	Location	Type	Required
user	query	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Calendly connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.listEventTypes.
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 Calendly API reference.

GET /scheduled_events

List scheduled events

Detail	Value
Operation ID	scheduling.listScheduledEvents
Method	GET
Path	/scheduled_events

Parameters

Name	Location	Type	Required
user	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Calendly connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.listScheduledEvents.
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 Calendly API reference.

GET /scheduled_events/{eventUuid}

Get a scheduled event

Detail	Value
Operation ID	scheduling.getEvent
Method	GET
Path	/scheduled_events/{eventUuid}

Parameters

Name	Location	Type	Required
eventUuid	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Calendly 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 Calendly API reference.

GET /scheduled_events/{eventUuid}/invitees

List event invitees

Detail	Value
Operation ID	scheduling.listInvitees
Method	GET
Path	/scheduled_events/{eventUuid}/invitees

Parameters

Name	Location	Type	Required
eventUuid	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Calendly connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.listInvitees.
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 Calendly API reference.

POST /scheduled_events/{eventUuid}/cancellation

Cancel an event

Detail	Value
Operation ID	scheduling.cancelEvent
Method	POST
Path	/scheduled_events/{eventUuid}/cancellation

Parameters

Name	Location	Type	Required
eventUuid	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Calendly connection from the Connection dropdown.
3. In the Operation dropdown, select scheduling.cancelEvent.
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 Calendly API reference.