List Tasks: ClickUp action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
List ID list_id	string	Required	List ID. Example: 123456789
Page page	string	Optional	Page number (starts at 0)
Include Subtasks subtasks	options	Optional	Include Subtasks. Options: No, Yes
Filter by Status statuses	string	Optional	Comma-separated status names

Sample request

{
  "list_id": "e.g. 123456789",
  "page": "0",
  "subtasks": "{{trigger.subtasks}}",
  "statuses": "e.g. to do, in progress"
}

Returns

{
  "tasks": [
    {
      "id": "abc123",
      "name": "Task 1",
      "status": {
        "status": "to do"
      },
      "priority": {
        "priority": "normal"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Tasks.

What does the List Tasks action do in ClickUp?

Retrieves tasks from a ClickUp list with filters for status, assignee, tags, due date, and custom fields. Used for digests, sprint reviews, or warehouse exports.

What inputs does List Tasks require?

Required: List ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if ClickUp returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Tasks support batch operations?

Yes. Run List Tasks inside a Loop node to process arrays. Tiny Command handles ClickUp's rate limits automatically so you don't have to throttle manually.

More actions