ActionClickUpUpdated September 2026

How do I list tasks in a ClickUp list?

Short answer: You can list tasks in ClickUp by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ClickUp List Tasks action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Tasks in ClickUp — start free All 9 ClickUp actions

List Tasks in ClickUp — start free

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.

Triggered by

Apps that pair well as the trigger for List Tasks.

Any of these apps can fire this action as part of a workflow.

Google Sheets → ClickUp

2 Google Sheets triggers

HubSpot → ClickUp

18 HubSpot triggers

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 run history shows the failed step with its input and the error message ClickUp returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Tasks support batch operations?

Run List Tasks inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within ClickUp's rate limits.

More actions