Get Task: 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
Task ID task_id	string	Required	Task ID. Example: abc123

Sample request

{
  "task_id": "e.g. abc123"
}

Returns

{
  "id": "abc123",
  "url": "https://app.clickup.com/t/abc123",
  "name": "Design landing page",
  "status": {
    "status": "in progress"
  },
  "priority": {
    "priority": "high"
  },
  "assignees": [
    {
      "username": "johndoe"
    }
  ]
}

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

FAQ

Questions about Get Task.

What does the Get Task action do in ClickUp?

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.

What inputs does Get Task require?

Required: Task 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 Get Task support batch operations?

Yes. Run Get Task 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