ClickUp - Create Task

↩ Part of the ClickUp integration.

Description

Creates a task in a ClickUp list (POST /list/{list_id}/task). It is the entry point of most ClickUp automations: a form is submitted, an order arrives or an incident is detected, and the task shows up in the right list with the right status and priority.

The destination list is identified by its id (list_id), never by its name.

Configuration

Field	Type	Required	Description
`credentials_id`	credentials	Yes	ClickUp credential
`list_id`	text	Yes	id of the list to create the task in
`name`	text	Yes	Task name
`description`	textarea	No	Description
`status`	text	No	Status (must already exist in the list)
`priority`	number	No	`1` urgent, `2` high, `3` normal, `4` low
`due_date`	text	No	Due date as a Unix timestamp in milliseconds
`assignees`	JSON	No	Assignee user ids as a JSON array, e.g. `[123,456]`

list_id, name, description, status and due_date are resolved through dynamic variables ({{data.field}}). priority is converted to a number and assignees is parsed as JSON — if it is not valid JSON it is simply ignored.

Credentials

This node requires a ClickUp credential (service type clickup):

Field	Description
`token`	Personal API token from ClickUp → Settings → Apps → API Token (starts with `pk_`)

Output

The task created by ClickUp, as the API returns it:

{
  "data": {
    "id": "86a1b2c3d",
    "name": "Order: ACME Inc.",
    "status": { "status": "to do", "type": "open" },
    "date_created": "1786700000000",
    "due_date": "1786788000000",
    "priority": { "id": "2", "priority": "high" },
    "url": "https://app.clickup.com/t/86a1b2c3d",
    "list": { "id": "901300123456", "name": "Incoming orders" }
  },
  "_meta": {
    "moduleVersion": "1.0.0",
    "success": true,
    "id": "86a1b2c3d",
    "url": "https://app.clickup.com/t/86a1b2c3d",
    "totalMs": 388
  }
}

Keep the id: it is what the update, comment and delete nodes need.

Usage Example

Task from a form

{
  "credentials_id": "clickup_ops",
  "list_id": "901300123456",
  "name": "Order: {{data.customer}}",
  "description": "{{data.details}}"
}

Urgent task with a due date and assignees

{
  "credentials_id": "clickup_ops",
  "list_id": "901300123456",
  "name": "Incident #{{data.ticket_id}}",
  "description": "Reported by {{data.email}}",
  "status": "to do",
  "priority": 1,
  "due_date": "1786788000000",
  "assignees": [ 4812345, 4812346 ]
}

Notes

If list_id or name is empty, the node stops with a validation error and does not call ClickUp.
due_date is milliseconds since the Unix epoch, not an ISO date. If you have an ISO string, convert it in a previous node (e.g. Date.parse(...) in an Execute Script node).
status must match a status configured in that list, letter for letter (ClickUp is case-insensitive but the status must exist), otherwise you get a validation error.
assignees takes numeric user ids, not emails or usernames.

ClickUp - Update Task — change the status once the work advances.
ClickUp - Add Comment — post progress on the task you just created.
ClickUp - List Tasks — check what the list already contains.