Create Task Comment
clickup.create_task_comment
ActionBusiness appsconnection required
Calls the ClickUp API with the connection's credentials.
Post a comment on a task, addressed by its 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
6 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 |
|---|---|---|---|---|---|
task_id The task id, e.g. '9hx' — the last segment of the task's URL. | string | Yes | — | — | — |
comment_text The comment body, as plain text. | string | Yes | — | — | — |
assignee User id to assign the comment to. | integer | No | — | ≥ 1 | — |
notify_all Notify everyone watching the task, not just the assignee. | boolean | No | false | — | — |
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. | boolean | No | false | — | — |
team_id The Workspace (team) id. Only needed — and then required — when custom_task_ids is on. | string | Conditional | — | only with custom_task_ids | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"custom_task_ids": false,
"notify_all": false
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The new comment's id. | string | — |
hist_id ClickUp's history id for the comment. | string | — |
date Creation time as a Unix timestamp in milliseconds. | number | — |
{
"date": 0,
"hist_id": "",
"id": ""
}See Create Task 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.