ClickUp n8n integrationAutomate ClickUp with n8n.

Adds a checklist to a task and gives the workflow somewhere to write the steps that follow. The checklist appears inside the task, under its own heading.

• Task ID: the task that receives the checklist, often {{ $json.id }} when a task node runs just before this one.
• Name: the heading of the checklist, which is where the phase or the owner usually goes.

Removes a checklist from its task, with every line it contains. Nothing is archived, so the operation belongs at the end of a branch you are sure about.

• Checklist ID: the identifier of the checklist itself, not of the task that holds it, a distinction worth double checking in the field mapping.

Two things can change on an existing checklist: what it is called, and where it sits among the other checklists of the task. The items inside stay untouched.

• Checklist ID: the checklist to edit.
• Name: under Update Fields, the new heading.
• Position: under Update Fields, a number that sets the rank of the checklist inside the task.

Writes one line inside an existing checklist and, if you want, hands it to someone in the same call.

• Checklist ID: the checklist that receives the line.
• Name: the text of the item, better written as the action to perform than as a topic.
• Assignee ID: under Additional Fields, the ClickUp user who owns that line.

Takes a single line out of a checklist and leaves the rest in place. Both identifiers are required, the parent checklist and the line itself.

• Checklist ID: the checklist the line belongs to.
• Checklist Item ID: the line to remove.

Edits a line without recreating it: new text, new owner, ticked or unticked, or moved underneath another line as a sub item.

• Checklist ID and Checklist Item ID: the line to edit and the checklist it sits in.
• Resolved: under Update Fields, the boolean that ticks the box.
• Parent Checklist Item ID: under Update Fields, nests the line underneath another checklist item.

Posts a comment on a task, a list or a view, and can notify everyone around that object at the same time.

• Comment On: the target type, task, list or view.
• ID: the identifier of that target, so a task identifier when Comment On is set to task.
• Comment Text: the body of the message.
• Notify All: under Additional Fields, sends the creation notification to everyone, the author of the comment included.

Erases one comment from the object it was posted on. Only the comment identifier is needed, and the deletion is final.

• Comment ID: the comment to remove, kept from the step that created it or read with comment.getAll.

Reads the comments attached to a task, a list or a view, and returns them as items the next node can loop over.

• Comments On: the type of object being read, task, list or view.
• ID: the identifier of that object.
• Limit: the maximum number of comments brought back, which keeps a long thread from flooding the execution.

Rewrites an existing comment in place, reassigns it, or marks it as resolved.

• Comment ID: the comment to edit.
• Comment Text: under Update Fields, the new body.
• Resolved: under Update Fields, marks the thread as handled.
• Assignee ID: under Update Fields, moves the comment to another ClickUp user.

Creates a folder inside a space, the container that will hold the lists of a project.

• Team Name or ID: the workspace. Fields labeled Name or ID read the values from your account and show them in a dropdown, and they also accept an identifier passed through an expression.
• Space Name or ID: the space that receives the folder.
• Name: the folder name, often the client or the project reference.

Deletes a folder from its space. The three location fields have to describe the same path, team, then space, then folder.

• Team Name or ID and Space Name or ID: where the folder currently lives.
• Folder Name or ID: the folder to delete, selected from the dropdown or given as an identifier.

Returns a single folder, which is the quickest way to check that it exists before writing anything into it.

• Team Name or ID and Space Name or ID: the path down to the folder.
• Folder Name or ID: the folder being read.

Lists the folders of a space and returns one item per folder, archived ones included or left out depending on the filter.

• Space Name or ID: the space to inspect, inside the team selected above it.
• Limit: the ceiling on the number of folders returned.
• Archived: under Filters, the boolean that decides whether archived folders come back too.

Changes the name of a folder. That is the single field this operation edits, nothing else about the folder moves.

• Folder Name or ID: the folder to rename, inside the team and the space you point at.
• Name: under Update Fields, the new name.

Opens a goal in the workspace, with its owners, its color and its deadline. Key results come afterwards, through their own operation.

• Team Name or ID: the workspace the goal belongs to.
• Name: the objective, written as a result rather than as a task.
• Due Date: under Additional Fields, the date the goal is measured against.
• Owners and Multiple Owners: under Additional Fields, who carries the goal, one person or several.

Takes a goal out of the workspace. The operation needs nothing but the goal identifier, so keep it from the step that created it or from a listing.

• Goal ID: the goal to delete.

Reads a single goal and returns it as one item, which is what you need before deciding whether to update it. Nothing is written back, so this is the safe half of a read then write pair.

• Goal ID: the goal to read.

Lists the goals of a workspace, one item per goal, ready to be filtered or counted further down the workflow.

• Team Name or ID: the workspace whose goals are listed.
• Limit: the maximum number of goals returned, useful on a workspace that has piled up years of objectives.

Edits a goal that already exists: its name, its description, its due date, its color, and the people on it, added or removed through two separate fields.

• Goal ID: the goal to edit.
• Due Date: under Update Fields, the new deadline.
• Add Owners and Remove Owners: under Update Fields, joining and leaving are handled independently of each other.

Attaches a measurable result to a goal. The type decides what gets counted.

• Goal ID and Name: the goal it belongs to, and what is being measured.
• Type: one of automatic, boolean, currency, number or percentage.
• Steps Start and Steps End: under Additional Fields, required for the Percentage, Automatic, Number and Currency types, they set the range progress runs over.
• Unit: under Additional Fields, only matters for Number and Currency, and for Currency it has to be a valid currency code.

Detaches a key result from its goal and deletes it. The goal itself stays where it is.

• Key Result ID: the key result to remove, which is not the goal identifier.

Moves the needle on an existing key result, or corrects the way it is described. Scheduled workflows call this one the most, because progress changes far more often than objectives do.

• Key Result ID: the key result being updated.
• Steps Current: under Update Fields, the value reached so far.
• Steps Start and Steps End: under Update Fields, the range, for the day the target itself is revised.
• Note: under Update Fields, a short comment on the update, useful when a figure drops.

Adds a list inside a ClickUp folder and returns it with its identifier, which the next nodes reuse to file tasks.

• Space Name or ID: the space that holds the list, picked from the dropdown or set by an expression, that is a value read from the previous node, such as {{ $json.space }}.
• Folderless List: left off, the list lands in the folder chosen just below.
• Name: the title of the list, the only text ClickUp requires here.
• Priority: in Additional Fields, an integer mapped as 1 Urgent, 2 High, 3 Normal, 4 Low.

Custom fields are declared list by list in ClickUp. Reading them returns each field definition, so a workflow knows which identifier to write to before it touches a task.

• Team Name or ID: the workspace, selected in the dropdown or set with an expression.
• List Name or ID: the list whose fields you want; the dropdown fills up once the space and the folder above are chosen.

Deleting a list removes it from the space along with what it holds. The node takes an identifier, never a name, and asks nothing before it fires.

• List ID: a plain text field at this step, usually {{ $json.id }} inherited from an earlier list operation.
• Folderless List: the switch still counts, since it tells the node where to look for the list.

One list, one read. The operation returns the record ClickUp keeps: title, content, dates, statuses and the folder it sits in.

• List ID: the identifier of the list to read, as text.
• Folder Name or ID: the folder n8n looks into, chosen from the dropdown.

Every list held by one folder comes back in a single call, each with its own identifier and dates.

• Folder Name or ID: the folder to scan.
• Limit: the maximum number of lists returned in one execution.
• Archived: in Filters, the switch that decides whether archived lists join the result.

Membership is read at list level. The operation returns the people who have access, each with the identifier the other ClickUp operations expect.

• List ID: the list to inspect, typed in or built with an expression.
• Return All: enabled, n8n walks every page of members; disabled, only the first ones come back.

An existing list is edited here. Only what you put in Update Fields moves, the rest of the record stays as it was.

• List ID: the list to edit.
• Name: in Update Fields, the new title.
• Unset Status: in Update Fields, clears the status set on the list.
• Priority: the same mapping as at creation, from 1 Urgent to 4 Low.

A tag belongs to the space, not to the task. This operation declares one, with the two colors that make it readable on a card.

• Space ID: the space where the tag is created, as text.
• Name: the label itself, and the exact spelling taskTag.add will ask for later.
• Foreground Color: the text color, taken from the picker.
• Background Color: the fill behind the label.

The tag disappears from the space. Tasks that carried it stay where they are, they simply lose the label.

• Space ID: the space the tag lives in.
• Name or ID: the tag to drop, selected from the list n8n loads from that space.

The inventory of tags declared in a space arrives in one go, names and colors included.

• Space ID: the space to read.
• Return All: checked, every tag comes back, however many there are.
• Limit: the ceiling when Return All stays unchecked.

A tag changes name or colors here. The operation wants the tag as it exists today and the new values side by side.

• Name or ID: the tag to modify, picked from the space list.
• New Name: the name to set for the tag.
• Foreground Color: the text color to apply.
• Background Color: the fill color to apply.

The task shows up in the chosen list and comes back with its identifier, which every later ClickUp operation in the workflow can reuse.

• List Name or ID: the list that receives the task, at the end of the team, space and folder chain.
• Name: the title of the task.
• Custom Fields JSON: in Additional Fields, values written as [ {"id": "", "value": ""} ].
• Time Estimate: in Additional Fields, an estimate expressed in minutes.

One identifier, one effect: the task leaves ClickUp. This operation carries no optional collection, nothing else to set, and no way back from the workflow.

• Task ID: the task to delete, often {{ $json.id }} handed over by the node before.

Reading a single task, with two switches that change what the answer contains.

• Task ID: the task to read.
• Include Subtasks: enabled, the subtasks come back with it.
• Include Markdown Description: enabled, the response carries markdown_description, which preserves the links and the formatting of the description.

Tasks come out of a list page by page, and the Filters collection is where the real selection happens.

• List Name or ID: the list to go through.
• Return All: enabled, n8n follows the pages until the list is exhausted.
• Include Closed: in Filters, closed tasks stay out of the response as long as this switch is off and no status filter is sent.
• Order By: in Filters, sorts on id, created, updated or dueDate.

Who is working on this task? The operation returns the members ClickUp shows on the card.

• Task ID: the task to inspect.
• Limit: the maximum number of members returned when Return All stays unchecked.

The operation writes one value into one custom field of one task. The field is addressed by its identifier, the one the list custom fields call gave back.

• Task ID: the task that carries the field.
• Field ID: the identifier of the custom field to fill.
• Value: the value to set.
• Value Is JSON: turn it on when the field expects an array, labels for instance, so n8n parses the value instead of sending plain text.

Editing in place. Everything optional lives in Update Fields, and what you leave empty keeps its current value.

• Task ID: the task to edit.
• Add Assignees: assignee identifiers, separated by a comma when there are several.
• Remove Assignees: the same format, for the people leaving the task.
• Status: the status to apply, written as text.

Declaring that one task waits for another happens here. ClickUp then knows the order, and the workflow does not have to hold it in a variable.

• Task ID: the task that waits.
• Depends On Task ID: the one that has to move first.

The link between two tasks breaks and each one becomes independent again. Same identifiers as at creation, in the same order.

• Task ID: the task that was waiting.
• Depends On Task ID: the one it was waiting for.

A task can live in several lists. This operation attaches an existing task to one more list, without moving it and without making a copy.

• Task ID: the task to attach.
• List ID: the list that receives it.

The task leaves one single list, the one you point at, and stays in the others where it appears. Nothing is deleted here, only the link between that task and that list.

• Task ID: the task to detach.
• List ID: the list it leaves.

A tag that already exists in the space is placed on a task, by name.

• Tag Name: the tag spelled exactly as it is in the space.
• Custom Task IDs: in Additional Fields, lets you point at the task through its custom identifier rather than the ClickUp one.
• Team Name or ID: in Additional Fields, read only when Custom Task IDs is on.

One single tag is taken off and the others stay on the task.

• Task ID: the task to clean up.
• Tag Name: the tag to remove, with the same spelling as in the space.
• Custom Task IDs: in Additional Fields, the switch that makes the node read a custom task identifier.

Writes a block of work that already happened onto a list, then hands back the saved entry.

• Start and Duration (Minutes): when the work began, and how long it ran, counted in minutes.
• Folderless List: says whether the target list sits outside a folder, while Space Name or ID, Folder Name or ID and List Name or ID finish the path under Team Name or ID.
• Additional Fields: carries Billable, Description, Assignee Name or ID and Tag Names or IDs.

Drops one entry from the workspace timesheet for good. Only the entry identifier matters here, so the operation behaves the same whatever list the time was sitting on.

• Time Entry ID: the identifier of the entry to remove, pasted by hand or read off the incoming item with an expression such as {{ $json.id }}, the n8n way of pointing at a value.
• Team Name or ID: the workspace holding that entry, chosen from the list or given by its id.

Reads a single entry and returns its stored values, which lets a workflow check a duration before acting on it.

• Running: switched on, the node returns only the timer currently ticking.
• Time Entry ID: the identifier of the entry to read.
• Team Name or ID: the workspace the lookup runs against.

Entries pile up fast on a busy workspace. This operation brings them back over a window of dates, one item per entry, ready to be added up or exported.

• Filters: holds Start Date and End Date, the two bounds of the period being asked for.
• Return All: on, n8n walks the API pages through to the last entry; off, Limit caps how many items come through.
• Team Name or ID: the workspace whose timesheet is read.

Starts a live timer on a task: the clock runs inside ClickUp until another operation stops it.

• Task ID: free text here rather than a dropdown, so the task identifier is typed in or taken from the item that fired the workflow.
• Additional Fields: Description says what the timer covers, and Billable flags it as client work from the first minute.
• Team Name or ID: the workspace the timer belongs to.

No identifier to pass here: the operation stops whatever timer is running in the workspace and leaves the rest of the timesheet untouched.

• Team Name or ID: the only field to fill in, which makes this one of the quickest operations to wire up.

Rewrites an entry already saved: a duration typed wrong, time logged against the wrong task, a billable box nobody ticked.

• Time Entry ID and Archived: the entry to fix, and the required boolean that states whether it is archived.
• Update Fields: what actually changes, from Duration (Minutes) and Start to Task Name or ID, Assignee Name or ID, Billable, Description and Tag Names or IDs.
• List Name or ID: where the entry sits, reached through Space Name or ID, Folderless List and Folder Name or ID.

Attaches one or more tags to entries that already exist, so time can be sorted later without touching the tasks themselves.

• Time Entry IDs: plural on purpose, several identifiers travel in one call and every entry named gets the same tags.
• Tags: a collection where each Add Tag row describes one tag to apply.
• Team Name or ID: the workspace those entries live in.

Sorting time by tag only works when everyone uses the same labels. This operation lists the ones a workspace already has for its entries.

• Return All: brings back the whole list by following the API pages; left off, Limit decides how many tags return.
• Team Name or ID: the workspace whose tags are read.

Takes tags off entries without touching the time logged on them.

• Tag Names or IDs: the tags to detach, picked from the list or passed as identifiers through an expression.
• Time Entry IDs: the entries to clean up, several at a time.
• Team Name or ID: the workspace involved.