Update Task

clickup.update_task
ActionBusiness appsconnection required

Calls the ClickUp API with the connection's credentials.

Change a task's name, description, status, priority, dates, estimate or parent, addressed by its task id. Custom field values are set with clickup.set_custom_field_value instead.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
ClickUp
Secret shape
the API token (pk_…), or {"token": "…"}
Config it needs
list_id
Resolved by
config.connection_id, else node.connection_id

Configuration

17 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
task_id
The task id, e.g. '9hx' — the last segment of the task's URL.
stringYes———
name
New task name.
stringNo———
description
New description, as plain text.
stringNo———
markdown_content
New description written in Markdown. ClickUp uses this in preference to description when both are set.
stringNo———
status
New status, by name — it must be one the task's List defines.
stringNo———
priority
Priority: 1 urgent, 2 high, 3 normal, 4 low.
integerNo—one of "1", "2", "3", "4"; 1–4—
due_date
Due date as a Unix timestamp in milliseconds.
integerNo—≥ 0—
due_date_time
True when due_date carries a time of day, not just a date.
booleanConditionalfalseonly with due_date—
start_date
Start date as a Unix timestamp in milliseconds.
integerNo—≥ 0—
start_date_time
True when start_date carries a time of day, not just a date.
booleanConditionalfalseonly with start_date—
time_estimate
Time estimate in milliseconds.
integerNo—≥ 0—
points
Sprint points for the task.
integerNo—≥ 0—
archived
Archive (true) or restore (false) the task.
booleanNo———
parent
Task id of the parent, to make this task a subtask of it.
stringNo———
extra_fields
Any further Update Task body keys, as a JSON object — this is how assignees are removed: {"assignees": {"rem": [183]}}.
stringNo—json format—
custom_task_ids
Treat task_id as the Workspace's custom task id (e.g. 'ABC-123') rather than ClickUp's own id. team_id becomes required when this is on.
booleanNofalse——
team_id
The Workspace (team) id. Only needed — and then required — when custom_task_ids is on.
stringConditional—only with custom_task_ids—
  • At least one of name, description, markdown_content, status, priority, due_date, start_date, time_estimate, points, archived, parent, extra_fields must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "custom_task_ids": false,
  "due_date_time": false,
  "start_date_time": false
}

Output

One shape.

result

The provider's response object, as returned.

Extra keys beyond the ones listed can appear.

{}

Notes

  • ClickUp ignores an empty body, so the node refuses to run unless at least one field is set.

See Update Task run in a workflow.

In a technical demo we add the ClickUp connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.