Update Comment
clickup.update_comment
ActionBusiness appsconnection required
Calls the ClickUp API with the connection's credentials.
Edit a comment's text, reassign it, or mark it resolved, addressed by its comment id rather than a task id.
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
4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
comment_id The comment id, from clickup.list_task_comments. | string | Yes | — | — | — |
comment_text The comment body. ClickUp requires it on every update, so restate it even when only resolving. | string | Yes | — | — | — |
assignee User id to assign the comment to. | integer | No | — | ≥ 1 | — |
resolved Mark the comment resolved (true) or reopen it (false). | boolean | No | false | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"resolved": false
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when ClickUp accepted the call. | boolean | — |
comment_id The comment that was updated. | string | — |
resolved The resolved state that was written. | boolean | — |
{
"comment_id": "",
"ok": false,
"resolved": false
}See Update Comment 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.