Add Task Assignee
clickup.add_task_assignee
ActionBusiness appsconnection required
Calls the ClickUp API with the connection's credentials.
Assign one or more people to a task by its task id, leaving whoever is already assigned in place.
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 |
|---|---|---|---|---|---|
task_id The task id, e.g. '9hx' — the last segment of the task's URL. | string | Yes | — | — | — |
assignee_ids User ids to add as assignees; ClickUp user ids are numbers. At least one is needed — ClickUp ignores an empty add list. | array | Yes | — | ≥ 1 characters; array of integer | [183] |
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.
{
"assignee_ids": [
183
],
"custom_task_ids": false
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Notes
- To unassign somebody use clickup.update_task with extra_fields {"assignees": {"rem": [183]}}.
See Add Task Assignee 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.