List Spaces: 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
Workspace/Team ID team_id	string	Required	Workspace/Team ID. Example: 1234567
Include Archived archived	options	Optional	Include Archived. Options: No, Yes

Sample request

{
  "team_id": "e.g. 1234567",
  "archived": "{{trigger.archived}}"
}

Returns

{
  "spaces": [
    {
      "id": "space123",
      "name": "Engineering",
      "statuses": [
        {
          "status": "to do"
        },
        {
          "status": "in progress"
        },
        {
          "status": "done"
        }
      ]
    }
  ]
}

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

FAQ

Questions about List Spaces.

What does the List Spaces action do in ClickUp?

Lists all spaces in a ClickUp workspace. Use as the first step before drilling into folders and lists.

What inputs does List Spaces require?

Required: Workspace/Team 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 Spaces support batch operations?

Yes. Run List Spaces 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