Skip to content
Floogos

ClickUp - Get Task

↩ Part of the ClickUp integration.

Description

Section titled “Description”

Reads a single ClickUp task by its id (GET /task/{task_id}) and passes the full object to the next node. Use it to check the current state before acting: which status the task is in, who is assigned, whether it is overdue, what its custom fields say.

Configuration

Section titled “Configuration”
FieldTypeRequiredDescription
credentials_idcredentialsYesClickUp credential
task_idtextYesTask id

task_id is resolved through dynamic variables ({{data.field}}). This node has no field selector: ClickUp returns the whole task.

Credentials

Section titled “Credentials”

This node requires a ClickUp credential (service type clickup):

FieldDescription
tokenPersonal API token from ClickUp → Settings → Apps → API Token

Output

Section titled “Output”

The task as ClickUp returns it (trimmed here for readability):

{
  "data": {
    "id": "86a1b2c3d",
    "name": "Order: ACME Inc.",
    "text_content": "3 units of SKU CAM-001",
    "status": { "status": "in progress", "type": "custom" },
    "date_created": "1786700000000",
    "due_date": "1786788000000",
    "priority": { "id": "2", "priority": "high" },
    "assignees": [ { "id": 4812345, "username": "ana", "email": "ana@acme.com" } ],
    "custom_fields": [],
    "list": { "id": "901300123456", "name": "Incoming orders" },
    "url": "https://app.clickup.com/t/86a1b2c3d"
  },
  "_meta": {
    "moduleVersion": "1.0.0",
    "success": true,
    "id": "86a1b2c3d",
    "totalMs": 205
  }
}

Note that dates come back as strings holding milliseconds ("1786788000000"), which is how ClickUp serializes them.

Usage Example

Section titled “Usage Example”
{
  "credentials_id": "clickup_ops",
  "task_id": "{{data.task_id}}"
}

A typical pattern is Get task → Decision on {{data.status.status}}, so the workflow only continues when the task reached a given stage.

Notes

Section titled “Notes”
  • A task that does not exist, or that lives in a space your token cannot see, returns a not_found error (404) and stops that branch.
  • The task id is the short code in the task URL (app.clickup.com/t/86a1b2c3d). If your workspace uses custom task ids, use the id ClickUp returns in the id field.
  • The response can be large (assignees, checklists, custom fields, tags). It is stored in the execution trace, so avoid reading tasks in a wide loop when you only need one field.
Section titled “Related Nodes”