Skip to content

ClickUp

The ClickUp nodes connect your workflows to ClickUp through its REST API v2. Use them to automate task management: create a task when an order comes in, change its status as a process advances, comment the result, or list a list’s tasks to process them.

There are six nodes, one per operation:

NodeOperationHTTP method
ClickUp: Create task (clickupCreateTask)Create a task in a listPOST /list/{list_id}/task
ClickUp: Get task (clickupGetTask)Read a task by its idGET /task/{task_id}
ClickUp: Update task (clickupUpdateTask)Update fieldsPUT /task/{task_id}
ClickUp: Delete task (clickupDeleteTask)Delete a taskDELETE /task/{task_id}
ClickUp: Add comment (clickupAddComment)Add a commentPOST /task/{task_id}/comment
ClickUp: List tasks (clickupListTasks)List a list’s tasksGET /list/{list_id}/task

The nodes use a ClickUp credential. Create it in Credentials → Add → ClickUp with this field:

FieldDescription
Personal API tokenThe personal token, from ClickUp → Settings → Apps → API Token (starts with pk_). Never shown in logs.

ClickUp authentication sends the token in the Authorization header as-is (no Bearer prefix). You can verify the credential with the Test button, which calls GET /user.

  • In ClickUp everything is referenced by id (strings): the list (list_id), the task (task_id). Get a list id from the list’s URL in ClickUp, or with the HTTP node over the spaces/folders/lists endpoints.
  • Dates (due_date) go as a Unix timestamp in milliseconds (number), not ISO text.
  • Priority is a number: 1 urgent, 2 high, 3 normal, 4 low.
ParameterTypeRequiredDescription
credentials_idcredentialYesClickUp credential
list_idtextYesList id
nametextYesTask name
descriptiontextNoDescription
statustextNoStatus (must exist in the list)
prioritynumberNo1 urgent, 2 high, 3 normal, 4 low
due_datetextNoUnix timestamp in milliseconds
assigneesJSONNoAssignee user ids, e.g. [123,456]

Output: the created task, including its id and url.

ParameterTypeRequiredDescription
credentials_idcredentialYesClickUp credential
task_idtextYesTask id
ParameterTypeRequiredDescription
credentials_idcredentialYesClickUp credential
task_idtextYesTask id
fieldsJSONYesFields to update, e.g. {"status":"in progress"}
ParameterTypeRequiredDescription
credentials_idcredentialYesClickUp credential
task_idtextYesid of the task to delete
ParameterTypeRequiredDescription
credentials_idcredentialYesClickUp credential
task_idtextYesTask id
comment_texttextYesComment text
notify_alltextNotrue to notify all assignees
ParameterTypeRequiredDescription
credentials_idcredentialYesClickUp credential
list_idtextYesList id
archivedtextNotrue to include archived
subtaskstextNotrue to include subtasks
pagenumberNoPage (pagination, 0-based)

Output: the array of tasks in the list.

Create a task from a form:

  • Node: ClickUp: Create task
  • list_id: 901300123456
  • name: Order: {{data.customer}}
  • description: {{data.details}}
  • priority: 2

Output:

{
"id": "86a1b2c3d",
"name": "Order: ACME Inc.",
"url": "https://app.clickup.com/t/86a1b2c3d",
"status": { "status": "to do" }
}

Each node classifies errors so the engine knows whether a retry makes sense:

SituationRetryableWhat to do
Validation (400)NoClickUp returns the reason (e.g. status not in the list, or invalid list_id). Fix the data.
Not found (404)NoThe task or list doesn’t exist. Check the id.
Authentication (401/403)NoInvalid token or no permission. Check the credential.
Server (500)YesTemporary ClickUp error; retried automatically.
Rate limit (429)YesClickUp’s Retry-After (~100 req/min) is honored and retried.
Network / TimeoutYesTransient issue; retried automatically.