ClickUp

Connect ClickUp with OAuth so agents can triage lists, review workload and status age, and change tasks through your Approvals

Connect ClickUp and CloudThinker agents can find what needs attention in a list, compare workload across assignees, read task discussions, documents, and chat channels, and update tasks through your approvals. You sign in with OAuth (you approve access on ClickUp’s own page), so there’s no API token to create or paste. You don’t need to look up list or task IDs either: agents read the workspace structure first and resolve names like “Platform Team” themselves.

Prerequisites

• A ClickUp account that can see the spaces and lists you want agents to work with.
• Edit permission on connections in your CloudThinker workspace.
• No existing ClickUp connection in this CloudThinker workspace. Each CloudThinker workspace holds one. To check, open ClickUp in More → Workspace settings → Connections. If it shows Connected, click Disconnect on its detail panel first.

Select exactly one ClickUp workspace when you authorize. ClickUp’s tools can’t switch workspaces after sign-in, and a connection authorized for several workspaces fails every request.

Setup

1. Open ClickUp in CloudThinker

   In the sidebar, click More → Workspace settings → Connections. On the Builtin Connections tab, search for ClickUp and click Connect.

2. Sign in to ClickUp

   ClickUp’s authorization page opens. Sign in with the account whose access matches what agents should see. If your browser is already signed in to a different ClickUp account, sign out there first.

3. Authorize one workspace

   Select the single ClickUp workspace CloudThinker should use, then approve access.

   Success state: you’re back in CloudThinker and the ClickUp connection shows Connected.

Connection details

Field	Description
OAuth authorization	Issued by ClickUp when you approve access, then stored encrypted by CloudThinker
ClickUp workspace	The one workspace you selected during authorization

Required permissions

Agents act as the ClickUp user who authorized the connection. They can read and change only what that user can, and changes show up in ClickUp under that user’s name.

Access	Covers	Approval
Read	Workspace hierarchy, lists, folders, tasks, custom fields, comments and threads, members, time entries, time in status, document pages, chat channels and messages	Runs without asking
Write	Create, update, move, or delete a task; add a comment; add or remove a tag; add or edit a page inside an existing Doc	A write, so Approvals decides

Authorize with a ClickUp user (or a dedicated service account) that can see only the spaces CloudThinker needs. Agents can never reach a space that user can’t open. A service account is an ordinary ClickUp user, so it counts as a member on your ClickUp plan. Invite it only to the spaces CloudThinker needs.

What agents can’t do

CloudThinker keeps a narrower tool set than ClickUp offers, so some actions are deliberately off, even with approval:

Not available	Why
Creating spaces, folders, lists, or Docs, or editing spaces, folders, and lists	Agents work inside your structure, they don’t reshape it. They can add or edit pages inside an existing Doc.
Merging tasks, deleting comments, editing someone’s comment	Can’t be undone, or changes a person’s own words
Starting or stopping time tracking	ClickUp has one running timer per user, so an agent could stop yours
Sending chat messages	Avoids unsolicited posts in human channels
Attachments, reminders, task dependencies and links	Out of scope for now

Agent capabilities

Capability	What agents can do
Workspace discovery	Map spaces, folders, lists, and recent work, and resolve names you type into ClickUp IDs
List triage	Find overdue, unassigned, and unscheduled tasks in one list
Workload review	Compare open work by assignee and status, and measure how long tasks sit in each status
Task investigation	Read task details, custom fields, comments, and threaded replies
Documents and chat	Read document pages and chat channel messages the connected user can see
Task changes	Create, update, move, or delete tasks, and change tags
Comments and docs	Add comments, and add or edit pages inside an existing Doc

When an agent plans several changes at once, such as retagging five tasks, the approval card lists every change before anything runs.

Verify the connection

Show the structure of our ClickUp workspace and list what needs attention in the biggest list

A working connection names your real spaces and lists, then returns overdue, unassigned, or unscheduled tasks from one of them. An authorization error means you need to reconnect.

Example prompts

List overdue, unassigned, and unscheduled tasks in the Platform Team → Sprint 42 list
Compare open ClickUp work by assignee in the Engineering space and flag anyone with more than 10 tasks in progress
Which tasks in the Backend list have been in "In review" the longest?
Read the comments on the oldest overdue task in Sprint 42 and suggest the next step
Move every task tagged blocked in Sprint 42 to Sprint 43 and add a comment explaining why

Troubleshooting

The OAuth page doesn't finish, or connects the wrong account

Your browser is probably signed in to a different ClickUp account. Sign out of ClickUp, sign in with the right account, then click Connect again.

Every request fails with a multiple-workspaces error

The connection was authorized for more than one ClickUp workspace. Open ClickUp in More → Workspace settings → Connections, click Disconnect on the detail panel, then click Connect and select exactly one workspace.

Requests suddenly fail with 401 Unauthorized

The ClickUp authorization expired or was revoked. Open ClickUp in More → Workspace settings → Connections and click Connect to sign in again.

The agent can't find a space, list, or task

The authorizing user may not have access, or the item moved. Confirm that user can open it in ClickUp, then ask the agent to read the workspace structure again.

Status age shows as unavailable

Time-in-status needs the Total time in Status ClickApp. A ClickUp workspace owner or admin can turn it on under ClickApps in the workspace settings. Task and workload reads keep working without it, and CloudThinker reports the measurement as unavailable rather than zero.

Requests fail with a rate-limit error

The ClickUp account hit its API quota. The limit depends on your ClickUp plan: see ClickUp’s rate limits. Wait for the window to reset, then retry the same request.

A change is stuck waiting

The write is waiting for a person. Look for the approval card in the chat and click Approve, or Notify approvers if you can’t approve yourself.

Security

• Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
• Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
• Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
• Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.

• One workspace per connection. Authorize only the ClickUp workspace CloudThinker should reach.
• Pick the authorizing user on purpose. Every read and write runs with that user’s ClickUp access. When they leave, reconnect with a different account.

Related

Approvals

Decide which ClickUp changes run on their own and which wait for a person

Asana Connection

Connect Asana for project health and task changes