ClickUp

All-in-one project management with tasks, docs, and goals via ClickUp API.

Detail	Value
Category	Project Management
Base URL	https://api.clickup.com/api/v2
Authentication	Bearer Token
Endpoints	6
Connector key	clickup

Using ClickUp in a workflow

1. Go to Connections and click New Connection.
2. Pick ClickUp 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 /list/{list_id}/task	Get tasks in a list
POST /list/{list_id}/task	Create a task in a list
GET /task/{task_id}	Get a task
PUT /task/{task_id}	Update a task
GET /team	Get authorized workspaces
GET /team/{team_id}/space	Get spaces in a workspace

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

GET /list/{list_id}/task

Get tasks in a list

Detail	Value
Operation ID	pm.listTasks
Method	GET
Path	/list/{list_id}/task

Parameters

Name	Location	Type	Required
list_id	path	string	Yes

Using this endpoint in a workflow

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

POST /list/{list_id}/task

Create a task in a list

Detail	Value
Operation ID	pm.createTask
Method	POST
Path	/list/{list_id}/task

Parameters

Name	Location	Type	Required
list_id	path	string	Yes

Request Body

Field	Type
name	string
description	string
priority	integer

Using this endpoint in a workflow

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

GET /task/{task_id}

Get a task

Detail	Value
Operation ID	pm.getTask
Method	GET
Path	/task/{task_id}

Parameters

Name	Location	Type	Required
task_id	path	string	Yes

Using this endpoint in a workflow

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

PUT /task/{task_id}

Update a task

Detail	Value
Operation ID	pm.updateTask
Method	PUT
Path	/task/{task_id}

Parameters

Name	Location	Type	Required
task_id	path	string	Yes

Request Body

Field	Type
name	string
status	string

Using this endpoint in a workflow

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

GET /team

Get authorized workspaces

Detail	Value
Operation ID	pm.listWorkspaces
Method	GET
Path	/team

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /team/{team_id}/space

Get spaces in a workspace

Detail	Value
Operation ID	pm.listSpaces
Method	GET
Path	/team/{team_id}/space

Parameters

Name	Location	Type	Required
team_id	path	string	Yes

Using this endpoint in a workflow

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