List Tasks

clickup.list_tasks

ActionBusiness appsconnection required

Calls the ClickUp API with the connection's credentials.

List the tasks in one List, addressed by its list id, 100 per page, with optional status, assignee and tag filters.

Connection

10 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
list_id The List id. Right-click the List in the sidebar, Copy link; the last URL segment.	string	Yes	—	—	—
page Page to fetch; ClickUp returns 100 tasks per page and pages start at 0.	integer	No	0	≥ 0	—
archived Return archived items instead of active ones.	boolean	No	false	—	—
include_closed Include tasks in a closed status.	boolean	No	false	—	—
subtasks Include subtasks alongside their parents.	boolean	No	false	—	—
order_by Field to sort by. ClickUp accepts id, created, updated or due_date.	string	No	—	one of "id", "created", "updated", "due_date"	—
reverse Reverse the sort order.	boolean	No	false	—	—
statuses Only tasks in these statuses, by name.	array	No	—	array of string	—
assignees Only tasks assigned to these user ids.	array	No	—	array of string	—
tags Only tasks carrying these tag names.	array	No	—	array of string	—

Every value below is the contract’s own example or default — nothing invented.

{
  "archived": false,
  "include_closed": false,
  "page": 0,
  "reverse": false,
  "subtasks": false
}

One shape.

Field	Type	Example
items One entry per row ClickUp returned.	array	—
count How many rows are in items.	number	—
last_page True when ClickUp says this was the final page; null when it did not say, which is not the same as 'no more rows'.	boolean	—

{
  "count": 0,
  "items": [],
  "last_page": false
}

ClickUp pages this 100 tasks at a time; read last_page to know whether to raise page and go round again.

In a technical demo we add the ClickUp connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.