18 ClickUp Connector
ClickUp is a personal live connection. It searches the signed-in member’s authorized workspace when a question is asked. It can also read Docs and apply one directly requested, audited task or Doc page update. ClickUp content is not copied into the workspace search index.
18.1 What is indexed or searched live
Nothing is indexed. A text search scans up to 300 recently updated tasks and returns at most 25 matches. Search checks the task title, description, status, tags, assignees, List, Folder, and Space. The answer reports this coverage, so an empty result does not claim that older tasks do not exist.
The live reader can also open one task ID, task URL, numeric List URL, View URL, Doc URL, or Doc page URL. It accepts https://app.clickup.com and a one-label enterprise *.clickup.com host. The supplied host is validated but never fetched. Nous always calls the fixed ClickUp API origin.
18.2 Administrator role and authentication
Each member connects one ClickUp workspace with their own personal API token. The token must start with pk_. It is sent only in the setup request body and is stored as a private member credential. Workspace and Team sharing do not apply.
18.3 Provider setup and permissions
- In ClickUp, open your personal settings and create or copy a personal API token under Apps.
- Confirm that the ClickUp account can open the workspace and tasks you need. The same account must be allowed to edit any tasks or Doc pages the member wants to update through Nous.
- In Nous, open Connectors, choose ClickUp, and paste the token.
- Nous discovers the workspaces authorized for that token. Select one when several are returned. You cannot type a workspace ID.
If the token can access one workspace, Nous selects it automatically. Existing connections receive the supported write actions automatically. There is no reconnect step, permission toggle, or separate confirmation setting.
18.4 Setup form fields
| Field | Required | Purpose |
|---|---|---|
| Connector name | Yes | A private label that helps the member recognize the connection. |
| ClickUp API Token | Yes | A personal token beginning with pk_. Whitespace is not accepted. |
| ClickUp workspace | Yes | One workspace returned by ClickUp for the submitted token. |
There are no refresh, pruning, indexing, workspace-access, or Team fields.
18.5 Workspace and Team access
The connection belongs to one member. Other members must connect their own ClickUp accounts. An administrator cannot make it public, assign it to a Team, add it to a document set, schedule scans, pause it, or reindex it.
18.6 Supported direct updates
A clear request in the member’s current chat message authorizes one immediate write. Nous does not ask for a second confirmation. Questions, previews, older messages, ClickUp content, and tool output do not authorize a write.
Supported task fields are name, markdown_content, status, and priority (1 to 4, or cleared). Supported Doc page fields are name, sub_title, and content. Page content can be replaced, appended, or prepended. Append and prepend are saved as one complete final replacement, so a replay cannot add the same text twice.
Each operation has a stable tenant-scoped ID and an audit row containing the request, authorization message, actor, target snapshot hash, and safe provider result. A replay of a completed or rejected operation makes no provider call. Nous rechecks the target immediately before writing and stops if it changed. A timeout or unverifiable result is marked uncertain and is never written again. After an uncertain append or prepend, inspect the page and request an explicit full replacement to recover.
Create, delete, archive, move, comment, custom-field, assignee, date, attachment, and bulk actions are not supported. Background, scheduled, Deep Research, Agent Service, and Digital Employee flows cannot write to ClickUp.
18.7 Supported links and testing
Test with non-sensitive tasks that the connected member can open:
- Ask for a recently updated task by words from two different supported fields. Confirm that the result names the bounded scan.
- Open a task by its ID, a short
/t/<task-id>URL, and a workspace task URL. - Open one numeric List URL shaped like
/<workspace-id>/v/li/<list-id>. - Open one View URL shaped like
/<workspace-id>/v/l/<view-id>. - Open a Doc and one page shaped like
/<workspace-id>/v/dc/<doc-id>/<page-id>. - Search for a phrase that has no match and confirm the query is not widened.
- Request one task field update and one page append in separate clear user messages. Confirm the provider values and audit rows.
- Try a dashboard URL shaped like
/<workspace-id>/v/db/...and confirm that Nous rejects it safely.
List and View reads return at most 25 tasks and say when more tasks are available.
18.8 Common errors
| Error | Action |
|---|---|
| No workspace appears | Check that the personal token belongs to the correct ClickUp account and that the account can open a workspace. |
| ClickUp rejects the token | Create a new personal token, paste it without spaces, and retry. |
| Permission error | Ask the ClickUp workspace owner to grant the member access to the required tasks. |
| Rate limit or temporary error | Wait briefly, then retry workspace discovery or the question. |
| A task is not found | Use a direct supported task link, or search with terms from a recently updated task. |
| Dashboard link is rejected | Use a task, List, View, Doc, or Doc page link. Dashboards are not supported. |
| A target changed before the write | Read the current item and make a new request with the intended values. |
| A write result is uncertain | Do not repeat it. Inspect the provider state. Use a full replacement after an uncertain append or prepend. |
18.9 Reconnect and remove
Use Reconnect to replace a token or change the selected authorized workspace. Removing a current private live connection disconnects it; there is no indexed ClickUp content to remove.
An older ClickUp row that indexed tasks shows Reconnect required, never Answered live. Choose Remove and reconnect. Nous removes the old pair and its indexed content, waits for removal to finish, and then opens the new private setup. It does not convert the old ownership or credential in place.