Update 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
Task Name name	string	Optional	Task Name
Description description	string	Optional	Description
Status status	string	Optional	Status name (must match a status in the list)
Priority priority	options	Optional	Priority. Options: Urgent, High, Normal, Low
Due Date due_date	string	Optional	Unix timestamp in milliseconds

Sample request

{
  "task_id": "e.g. abc123",
  "name": "{{trigger.name}}",
  "description": "{{trigger.description}}",
  "status": "e.g. complete",
  "priority": "{{trigger.priority}}"
}

Returns

{
  "id": "abc123",
  "name": "Updated task",
  "status": {
    "status": "complete"
  }
}

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

FAQ

Questions about Update Task.

What does the Update Task action do in ClickUp?

Updates an existing ClickUp task: name, description, status, assignees, due date, priority, or custom fields. Only the fields you pass are changed.

What inputs does Update 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 Update Task support batch operations?

Yes. Run Update 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