ClickUp Connector

Coppermind's ClickUp connector polls one or more ClickUp lists for task activity and ingests it into the client mind(s) you map. The default connect flow is Sign in with ClickUp (OAuth) — no API token to paste.

Connect#

1. Open hq.coppermind.app → Connectors → ClickUp.
2. Click Connect ClickUp and sign in with ClickUp in the browser tab that opens, authorizing your workspace.
3. Coppermind stores the authorization and auto-selects your workspace (if you authorized more than one, the first is used), then shows the connector as connected.

Manual fallback: the MCP connectors tool still accepts a ClickUp personal API token (clickup_api_token, from ClickUp Settings → Apps) plus a workspace (team) ID (clickup_team_id, visible in the ClickUp URL) for setups where OAuth isn't possible. Existing token-based connections keep working unchanged.

Connecting the workspace does not start ingesting anything by itself — you still need to map lists to client minds (step below). This mirrors how the Google Drive connector works (#1990): one connection, many list→mind mappings.

Map lists to clients#

In the same Connectors tab, open the ClickUp mapping table. It lists every list Coppermind can see (with its space/folder for context) alongside a dropdown of your client minds. Assign a list to a client, and new/updated tasks in that list start flowing into that client's memory within about 15 minutes.

Multiple ClickUp lists can feed the same client mind (e.g. a "Sprint Board" and a "Bugs" list both mapped to the same client), and unmapping one list never affects another's mapping.

There is no chat-based ("ask Claude") way to do this mapping — it's dashboard-only, matching the Drive connector.

What gets ingested#

Each poll pulls tasks updated since the last poll (or, on first connect, ClickUp's default recent history) from every mapped list. For each task, Coppermind stores:

• Task name
• Status
• Assignees
• Description / content
• Last updated time

Not yet supported: ClickUp Docs. This v1 connector only ingests tasks. Docs support is a known gap, tracked as a fast-follow — do not tell a customer their ClickUp docs are being synced.

Disconnect#

Disconnecting the workspace connector (or unmapping an individual list) stops future polling for that scope. Memories already ingested are retained.

Troubleshooting#

• No lists showing up: reconnect via Sign in with ClickUp and make sure you authorize the right workspace. (Manual-token setups: confirm the personal API token has access to the workspace, and that the workspace ID matches the one in the ClickUp URL.)
• Tasks not appearing after mapping a list: allow up to 15 minutes for the next poll cycle; check connectors action=status (or the dashboard connector detail) for auth or rate-limit errors.