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, update a task or Doc page, and create tasks, private Docs, and Doc pages after the member confirms the exact proposal. 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

  1. In ClickUp, open your personal settings and create or copy a personal API token under Apps.
  2. Confirm that the ClickUp account can open the workspace and tasks you need. The same account must be allowed to edit or create the tasks, Docs, and Doc pages the member wants to manage through Nous.
  3. In Nous, open Connectors, choose ClickUp, and paste the token.
  4. 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 confirmed changes

When a member requests a supported change, Nous validates it and replies in the normal chat with confirmation text generated from the exact staged operation. ClickUp remains unchanged at this point. The member can confirm naturally with replies such as Yes, Go ahead, or OK, update it and give me the link. Nous then applies that proposal once and returns the verified ClickUp link in the chat.

A question about the proposal does not discard it. The member can ask whether an append keeps existing images, receive an answer, and then confirm on the same conversation branch. Changing the target, destination, fields, or content creates a new proposal. Cancelling invalidates the old proposal. ClickUp content, older confirmations, assistant text, and tool output cannot authorize a change.

The confirmation identifies the action and target or destination. It states the requested names, subtitles, status, priority, visibility, and content mode. A replaced or superseded proposal requires a new confirmation and cannot silently select an older pending change.

Supported task fields are name, description, status, and priority (1 to 4, or cleared). Task descriptions and Doc page content can be replaced, appended, or prepended. For append and prepend, Nous reads the complete current content from ClickUp and composes the final value on the server. It does not rebuild content from search snippets, so existing Markdown and images remain intact. The final value is stored as one operation, so replay cannot add the same text twice.

Supported creation operations are:

  • a task in an existing List, with a name and optional description, status, and priority;
  • a private Doc in the connected workspace, an existing Space, Folder, or List, optionally with its first named page;
  • a root page or nested page in an existing Doc, with a name and optional subtitle and content.

Nous uses only destinations that it resolved in the connected workspace. If a name matches several destinations, the member must choose one. Docs created by this connection are private; creating public Docs or changing permissions is not supported.

Each operation has a stable tenant-scoped audit record containing the request, confirmation version, member reply, actor, target snapshot, and safe provider result. The confirmation remains attached to the proposal the member saw. Replaying a completed or rejected operation makes no provider call. Nous rechecks existing targets immediately before writing and stops if they changed.

Creation requests are never blindly retried after a timeout or lost response. For a Doc with a first page, Nous records the created Doc before creating the page. If the page then fails, it returns the Doc link and can resume only the missing page when the recorded outcome proves that retry is safe. It never creates a second Doc to recover the page.

Delete, archive, move, comment, custom-field, assignee, date, attachment, public-Doc, permission, and bulk actions are not supported. Creating Lists, Folders, or Spaces is also outside this connection. Background, scheduled, multi-model comparison, 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:

  1. Ask for a recently updated task by words from two different supported fields. Confirm that the result names the bounded scan.
  2. Open a task by its ID, a short /t/<task-id> URL, and a workspace task URL.
  3. Open one numeric List URL shaped like /<workspace-id>/v/li/<list-id>.
  4. Open one View URL shaped like /<workspace-id>/v/l/<view-id>.
  5. Open a Doc and one page shaped like /<workspace-id>/v/dc/<doc-id>/<page-id>.
  6. Search for a phrase that has no match and confirm the query is not widened.
  7. Request a task-description append on content containing an image. Confirm that the proposal does not change ClickUp, reply OK, update it and give me the link, and verify that the image and existing text remain.
  8. Create a task in a test List, a private Doc with its first page, and a nested page. Confirm each proposal once and verify its returned link.
  9. Ask a question about a proposal before confirming, then change another proposal and confirm that only the new version can run.
  10. 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 proposal was replaced or cancelled Ask Nous to prepare the current operation again; an older proposal cannot run.
A write or creation result is uncertain Do not repeat it. Inspect the provider state and use the recorded result link when available.
A Doc exists but its first page failed Open the returned Doc link. Ask Nous to resume only the missing page; do not request another Doc.

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.

18.10 Official provider documentation