ClickUp Custom icon

ClickUp Custom

Consume ClickUp Custom API
Join our community

Actions2

Overview

This n8n node allows you to create new tasks in ClickUp via its API. It is designed for automation scenarios where you need to programmatically add tasks to specific lists within your ClickUp workspace, optionally setting a wide range of task properties such as assignees, tags, custom fields, due dates, priorities, and more.

Common use cases:

  • Automatically creating tasks from form submissions or support tickets.
  • Generating tasks based on events in other systems (e.g., CRM, helpdesk).
  • Bulk task creation with dynamic assignment and metadata.

Practical example:
When a new lead is added in your CRM, this node can create a corresponding task in ClickUp, assign it to the sales team, set a due date, and tag it appropriately.

Properties

Name Type Meaning
Authentication options Selects the authentication method: Access Token or OAuth2.
Team Name or ID options The ClickUp team (workspace) where the task will be created. Can be selected from a list or specified by ID/expression.
Space Name or ID options The space within the team where the task will reside. Can be selected from a list or specified by ID/expression.
Folderless List boolean Determines if the target list is folderless. If true, selects from folderless lists; otherwise, selects a folder first.
Folder Name or ID options The folder containing the list (if not folderless). Can be selected from a list or specified by ID/expression.
List Name or ID options The specific list where the task will be created. Can be selected from a list or specified by ID/expression.
Name string The name/title of the new task. Required.
Additional Fields collection Optional additional properties for the task (see below).

Additional Fields (collection):

Name Type Meaning
Assignee Names or IDs multiOptions Assign users to the task. Select from list or specify IDs/expressions.
Custom Fields Text fixedCollection Set custom text fields by field name/ID and value.
Custom Fields Options fixedCollection Set custom dropdown/label fields by field name/ID and value.
Use Date Time On Custom Fields boolean If true, enables time option for custom fields.
Content string Task description/content. Supports markdown if "Is Markdown Content" is enabled.
Due Date dateTime The due date for the task.
Due Date Time boolean Whether to include time information with the due date.
Is Markdown Content boolean If true, treats the content as markdown.
Notify All boolean If true, notifies all watchers of the task.
Parent ID string Sets the parent task ID (for sub-tasks).
Priority number (1–4) Task priority: 1=Urgent, 2=High, 3=Normal, 4=Low.
Start Date dateTime The start date for the task.
Start Date Time boolean Whether to include time information with the start date.
Status Name or ID options The status to assign to the task.
Tag Names or IDs multiOptions Tags to apply to the task.
Time Estimate number Estimated time to complete the task, in minutes.

Output

The node returns the response from the ClickUp API after creating the task. The output structure typically includes:

{
  "id": "task_id",
  "name": "Task Name",
  "status": { ... },
  "assignees": [ ... ],
  "tags": [ ... ],
  "priority": 3,
  "due_date": 1681234567890,
  "start_date": 1681230000000,
  "custom_fields": [ ... ],
  ...
}
  • The exact fields depend on the data sent and the ClickUp API's response.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error property with the error message.

Dependencies

  • External Service: Requires access to the ClickUp API.
  • Authentication: Needs either a ClickUp Access Token or OAuth2 credentials configured in n8n.
  • n8n Credentials: Must have "ClickUp API" or "ClickUp OAuth2 API" credentials set up in your n8n instance.

Troubleshooting

Common Issues:

  • Missing required fields: If mandatory fields like "Name" or "List" are not provided, the node will throw an error.
  • Invalid IDs: Supplying incorrect team, space, folder, or list IDs will result in API errors.
  • Custom Fields: If no custom fields are provided when required, the node may throw a "Minimum 1 Custom Fields to Setting" error.
  • Authentication errors: Invalid or expired tokens will cause authentication failures.

Error Messages:

  • "Minimum 1 Custom Fields to Setting": Occurs if you attempt to set custom fields but provide none. Ensure at least one custom field is specified.
  • API error messages from ClickUp (e.g., "Not Found", "Unauthorized"): Check your credentials and input values.

How to resolve:

  • Double-check that all required fields are filled.
  • Verify that IDs correspond to existing resources in ClickUp.
  • Ensure your authentication credentials are valid and have sufficient permissions.

Links and References

Discussion