Start free
ActionClickUpUpdated June 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.

Use this actionAll 9 ClickUp actions
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
List ID
list_id
stringRequiredList ID. Example: 123456789
Page
page
stringOptionalPage number (starts at 0)
Include Subtasks
subtasks
optionsOptionalInclude Subtasks. Options: No, Yes
Filter by Status
statuses
stringOptionalComma-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.

Gmail → ClickUp
1 Gmail triggers
Slack → ClickUp
13 Slack triggers
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 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. TinyCommand handles ClickUp's rate limits automatically so you don't have to throttle manually.
More actions

Other ClickUp actions.

Action
Add Comment
Adds a comment to a ClickUp task, optionally as a specific user with @mentions. Used for automation activity logs, AI summary notes, or status broadcasts.
Action
Create Task
Creates a new task in a ClickUp list with name, description, assignees, status, priority, due date, tags, and custom fields. The standard write action for piping forms or external tickets into ClickUp.
Action
Delete Task
Deletes a task from ClickUp by ID. Moves to trash for 30 days before permanent deletion, so this is recoverable in the short term.
Action
Get Task
Retrieves a ClickUp task by ID with name, description, status, assignees, due date, parent, list, and custom fields. The standard read after a trigger fires with an ID.
Action
List Folders
Lists all folders in a ClickUp space along with their IDs and names. Use to populate a folder picker before creating a list.
Action
List Lists
Lists all lists in a ClickUp folder. Required step before creating a task, since tasks live inside lists.