ClickUp
Read and write ClickUp work - walk Workspaces, Spaces and Lists, page through tasks, create, update, archive and delete them, and work their comment threads.
Connect a ClickUp Workspace with a personal API token to run its work end to end: list the Workspaces, Spaces and Lists the token can reach - each List with its own status vocabulary and ClickUp's own task count - page through a List's tasks, read one in full by native or custom id, create tasks and subtasks with status, priority, assignees, tags and dates, update or archive them, delete them, and read and post task comments. Everything written through this connection is attributed in ClickUp to the person whose token it is.
Connect
| Credential field | Required | Where it comes from |
|---|---|---|
API token (API_TOKEN) | Yes | From Settings → Apps → API Token (pk_…). It carries the full access of the user who created it - there are no scopes to narrow it - and every write is attributed to them. |
Tools
| Tool | Access | What it does |
|---|---|---|
Whoami (yekar.clickup.whoami) | Read | The ClickUp user this connection's token belongs to. Run it first - every other tool is scoped to this person's own access, and their user id is what the assignee filters take. |
List workspaces (yekar.clickup.list-workspaces) | Read | The ClickUp Workspaces this token's user belongs to. A Workspace id is the root of everything else - Spaces, Lists and tasks all hang off one - and it is also what a custom task id needs to resolve. |
List spaces (yekar.clickup.list-spaces) | Read | The Spaces in a Workspace. A Space is the second level of ClickUp's hierarchy (Workspace → Space → Folder → List → task) and is what List lists takes. |
List lists (yekar.clickup.list-lists) | Read | The Lists in a Space (folderless) or in a Folder, each with its own status vocabulary and ClickUp's own task count. A List id is what List tasks and Create task require - a List name is never accepted. |
List tasks (yekar.clickup.list-tasks) | Read | A page of tasks from one List. Closed tasks are hidden unless you ask for them - a finished task disappears from this endpoint rather than coming back marked done. ClickUp reports no total and its page size is fixed at 100. |
Get task (yekar.clickup.get-task) | Read | One task in full - description, status, priority, assignees, dates, tags and custom field values. Accepts a native ClickUp id, or a human-readable custom id (ABC-123) when customTaskIds and workspace are both given. |
Create task (yekar.clickup.create-task) | Write | Create a task in a List, optionally as a subtask. Its status must come from that List's own vocabulary. ClickUp has no dry run: the task exists as soon as this returns. |
Update task (yekar.clickup.update-task) | Write | Change a task - rename it, rewrite its description, move its status, set or clear priority and dates, add or remove assignees, or archive it. Only the fields you pass are touched. A status must belong to the List the task is in. |
Delete task (yekar.clickup.delete-task) | Write | Delete a task and its subtasks. Nothing in the API undoes this. Update task with archived: true is the reversible operation and is almost always what is wanted instead. |
List task comments (yekar.clickup.list-task-comments) | Read | The most recent comments on a task, newest first. ClickUp returns 25 at a time and reports no total; walk further back by passing the returned oldest pair as start and startId. |
Add task comment (yekar.clickup.create-task-comment) | Write | Post a comment on a task, attributed to the user whose token this connection holds. It can be assigned to someone, which puts it in their ClickUp inbox. There is no draft state and no unsend. |
Notes
- Create a token in ClickUp under Settings → Apps → API Token (it starts with pk_) and paste it here.
- A personal API token IS that person: it carries exactly their access, no more, and every task, status change and comment made through this connection appears in ClickUp under their name. Bind automations using this integration as service connections so the attribution is a role rather than an individual's side effect.
- There is no scope picker on a ClickUp personal token - the only ceiling is the access of the user who created it, plus the operations ClickUp reserves for Workspace owners and admins. Create it from an account whose reach matches what the automation should be able to touch.
- ClickUp's API calls a Workspace a "team" in every path and payload, while its UI calls it a Workspace. They are the same thing. Run List workspaces first - its id is the root of everything else.
- Statuses are defined PER LIST, not per Workspace. List lists returns each List's own statuses, and those exact strings are the only ones a write to that List may use; a status borrowed from another List is rejected.
- Finished tasks disappear from List tasks unless includeClosed is set - ClickUp hides anything in a closed-type status rather than returning it marked done.
- Priority is inverted in ClickUp's storage (1 is the most urgent), so every tool here takes the word - urgent, high, normal, low - and converts.
- Rate limits are per minute and per token: 100 requests on Free and Unlimited, more on Business and above, shared by everything using that token.
- Add one credential per token - a production and a sandbox token can live on the same connection.