ConnectorsClickUp

Connect ClickUp

Connect ClickUp with a personal API token, see which spaces and tasks Gurusup reads, bring in past tasks, and fix token errors.

Admins only. Gurusup can tell you why a task is blocked by joining its comments with the Slack thread and the customer call it came from. Gurusup only reads ClickUp: the one thing it creates there is its own webhook, so it hears when tasks change.

At a glance

TopicDetails
Who can connectAdmins
What you needA ClickUp personal API token (starts with pk_)
What Gurusup readsTasks in spaces shared with the whole ClickUp workspace
How changes arriveWithin minutes through a webhook, plus a daily check
Past contentImport history, from last week to last year
Knowledge accessDefault access, Restricted or Private. See Who can read it.

Before you start

  • You are an admin in Gurusup. If a member tries, Gurusup says "Only organization admins can connect ClickUp. Ask an admin to connect it."
  • You have a ClickUp personal API token from a regular member account, not an admin, as the token steps ask. You create it in ClickUp under Settings > Apps.
  • Gurusup reads the spaces that are shared with the whole ClickUp workspace and that this account can see.
  • ClickUp takes one connection per organization, and one connection reads one ClickUp workspace.

Connect ClickUp

Open the ClickUp connector

In the sidebar, open Sources, then Catalog, find ClickUp (use Search sources if you need to) and click Connect on its row. Its page opens. Next to Organization accounts, click Connect for the organization. The dialog Connect ClickUp for the organization opens.

Create the token in ClickUp

Under the Personal access token field, the hint reads "Sign in with a regular member account, not an admin." and Show steps adds "Under Settings → Apps, generate a personal API token." Do that in ClickUp and copy the token.

Paste the token

Paste it in Personal access token. Gurusup says "Reading the spaces this token reaches in ClickUp…" and then shows Spaces Gurusup will read in with your ClickUp workspace name, Signed in as with the ClickUp user, and the list of spaces. If the token reaches more than one ClickUp workspace, pick one in Workspace.

Check what stays out

If the token sees private spaces, a line says how many stay out, for example "2 private spaces this token sees stay out: Gurusup only reads spaces shared with the whole workspace." With no shared space yet, the list reads "No shared spaces yet".

Choose who can read it (optional)

Under Who can read it, Access mode starts as Default access. Choose Restricted or Private to limit the source to the people you pick.

Connect

Click Connect (it stays off until Gurusup has read the spaces). A message says "ClickUp connected." and the connection appears under Organization accounts with a Connected badge.

From now on, Gurusup picks up tasks that are created or change in the shared spaces. Tasks that do not change come in only when you import past work.

What Gurusup reads

Gurusup makes one document per task. A subtask is a task too, so it gets its own document, and its parent lists it.

PartWhat Gurusup reads
The taskName, where it lives (space, folder and list), status, assignees, priority, tags, a link to open it in ClickUp, the parent task, and the created, updated, start, due and closed dates
Custom fieldsEach custom field that has a value
DescriptionThe task description
ChecklistsEach checklist with its items, ticked or not
SubtasksA list of the subtasks with their status and a link
CommentsEvery comment and its replies, with who wrote it and when
ReferencesIssue keys and links to Linear, Jira or GitHub in the task, so Gurusup can join them with the same work in other sources

What Gurusup does not read

Left outDetail
Private spacesOnly spaces shared with the whole ClickUp workspace are read.
AttachmentsA task's document does not include them.
Time trackingA change that only touches time spent, time estimate or time tracked does not trigger a new read.

Private lists inside shared spaces are not filtered out, so they can come in.

How changes arrive

  • Within minutes. Gurusup creates a webhook in your ClickUp workspace. ClickUp tells Gurusup when a task is created, changes or is deleted, and when a list, folder or space is deleted or a space changes. Gurusup then reads the task again.
  • Once a day. Gurusup looks for tasks that changed since its last check, and checks its webhook is still in place. Anything the webhook missed comes in then.
  • Deleted or moved out. When a task, its list, folder or space is deleted, or the space becomes private, Gurusup withdraws the task: what it learned only from that task leaves, and anything other sources also back stays.

Gurusup does not copy who can see a space in ClickUp. Within the shared spaces, the access you set in Gurusup is what counts.

Import past work

Until you import, History says "Only new content comes in until you import past content."

Open Import history

On Sources, open the ClickUp page. Under History, click Import history.

Pick how far back

Pick Last week, Last month, Last 3 months, Last 6 months or Last year. Gurusup counts the tasks changed in that window in your shared spaces, for example "~120 tasks", or "500+ tasks" when there are more than it counts, and shows what the import would use out of what you have left this month, in euros.

Import

Click Import. The message reads "Importing history. It keeps going in the background." What does not fit in your remaining usage waits until it renews.

A window you already imported shows "Already imported". If the import stops, the button reads Try again.

Who can read it

ClickUp is one source.

Knowledge accessWho reads it in Brain
Default accessEveryone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them.
RestrictedOnly the people you pick. Administrators are not included unless you pick them.
PrivateOnly you. Administrators are not included.

Set it when you connect, so it applies before Gurusup reads anything. To change it later, open the ClickUp page and change Access mode under Knowledge access. It saves as soon as you change it, and it covers only what arrives after that. See Restrict a source to specific people.

Check that it worked

  1. On Sources, a row named "ClickUp: " followed by your ClickUp workspace name is there.
  2. Change a task in a shared space, for example add a comment.
  3. Open Ingest and pick the ClickUp source in the source filter. The task moves from Queued to Learning to Learned. See Follow ingestion.

Reconnect

Open the ClickUp page from Sources. Under Organization accounts, the account shows its status and when it last synced. The page does not list the spaces Gurusup reads; you see them in the Connect ClickUp for the organization dialog before you connect, and again when you reconnect.

To swap the token, click Reconnect on the account's row, paste a new one and click Reconnect again. Gurusup keeps the connection, its access and what it learned. The token has to reach the same ClickUp workspace.

If ClickUp stops accepting the token, for example because it was deleted, the status reads Needs reconnect. Click Reconnect on the account's row and paste a new token. Until you reconnect, Gurusup reads nothing new from ClickUp.

Disconnect

On Sources, open the ClickUp page. Under Danger zone, open the menu on Disconnect, choose Disconnect and confirm. Gurusup deletes its webhook in ClickUp and forgets the token, which stays in ClickUp under Settings > Apps until you delete it. A ClickUp source has no Remove source while it is connected. See Remove, disconnect and what stays.

If it does not work

Some messages show under the token field as soon as you paste it. After Connect or Reconnect they start with "Could not connect ClickUp.", and after Disconnect with "Could not disconnect."

MessageWhat to do
"ClickUp didn't accept this token. Create a new personal API token in ClickUp under Settings → Apps and paste it here."The token is wrong or was deleted. Create a new one and paste it.
"This token can't read that ClickUp workspace. Use a token from a member of the workspace."Use a token from someone who belongs to that ClickUp workspace.
"Choose the ClickUp workspace to connect."The token reaches several ClickUp workspaces. Pick one in Workspace.
"Choose the same ClickUp workspace to reconnect. Add a new connection for another workspace."Paste a token that reaches the workspace already connected.
"Paste a ClickUp personal API token from Settings → Apps."What you pasted is not a personal API token. It starts with pk_.
"Gurusup reads spaces shared with the whole workspace, and none are yet."Share a space with the whole ClickUp workspace, or use a token that sees one.
"ClickUp needs to be reconnected with a new personal API token."ClickUp refused the token. Paste a new one and click Reconnect.
"Gurusup couldn't read ClickUp just now. Try again in a minute, and contact support if it keeps failing."Wait a minute and paste the token again.
"We couldn't read ClickUp because of a problem on our side. Your connection is unchanged. Contact support for help."Contact support.
"We couldn't disconnect ClickUp because of a problem on our side. Your connection is unchanged. Contact support for help."Contact support.
"The import didn't finish. Try again, and contact support if it keeps failing."Click Try again. If it keeps failing, contact support.
"Ingestion is paused for this organization. Ask your organization admin to resume ingestion before adding content." or "Demo Mode prevents changing external sources. Ask your organization admin to turn off Demo Mode to continue."Connecting, reconnecting and changing what a source brings in are off. Disconnect still works while ingestion is paused, but not in Demo Mode. See Connectors overview.

Nothing coming in and no message? See Connector troubleshooting.