Skip to main content

​
About ClickUp

Iru reads workspaces, spaces, folders, lists, tasks, and members from the ClickUp API. ClickUp personal tokens look like pk_… and must be sent as the raw Authorization header value - do not prefix Bearer, or authentication fails.

​
How It Works

Authorization: pk_XXXXXXXXXXXXXXXX
DetailValue
CategoryWork management
AuthenticationPersonal API token (pk_…)
Official references: Authentication, API reference, Help Center.

​
Prerequisites

  • ClickUp user who is a member of every workspace you want evidence for.

​
Connect ClickUp to Iru

Complete this tab before you connect the source in Compliance.
1

Sign in to ClickUp

Open ClickUp and sign in with a user who is a member of every workspace Iru should read.
2

Open your avatar menu

Select your Avatar (profile photo or initials) in the lower-left or header, depending on your ClickUp layout.
3

Open Settings and Apps

Choose Settings, then Apps (or ClickApps / Integrations if your tenant routes API tokens there; use the path that exposes API Token).
4

Open API Token

Select API Token to view existing tokens and the control to create a new one.
5

Generate a personal API token

Select Generate (or Create token) to mint a new pk_… token.
6

Copy the token value

Copy the full pk_ string. Regenerate invalidates the prior token, so update Iru the same day if you rotate.
Continue on the Iru Compliance tab.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Remove Bearer - only the token string belongs in the header.
Token’s user must join that workspace.
Paste the new pk_ token in Iru.

Sources Management

Browse and manage every Compliance source.

Getting Started With Compliance

Frameworks, actions, and Artifacts.

Iru Overview

How Endpoint, Compliance, and Identity fit together.

Artifacts Management

Upload, review, and organize evidence from sources and actions.