# ClickUp API tokens (/integrations/clickup-service-account)





Connect ClickUp with a personal API token. The workflow acts with the permissions of the user who created the token.

Tokens are bound to the user who creates them: every action a workflow takes is attributed to that user, and workflows can lose access if the user is deactivated or removed from a workspace. For production workflows, create the token from a dedicated service user (e.g. `sim-bot@yourcompany.com`) rather than a personal account.

## Prerequisites [#prerequisites]

In Sim, you need workspace write access and permission to manage integrations.

A ClickUp account with access to the workspaces your workflows need. Any user can generate a personal API token from their settings.

## Creating the API token [#creating-the-api-token]

<Steps>
  <Step>
    Log in as the service user, click your avatar in ClickUp, and open **Settings**
  </Step>

  <Step>
    In the sidebar, go to **Apps**, then find **API Token**
  </Step>

  <Step>
    Click **Generate** to create your personal token
  </Step>

  <Step>
    Copy the token — it starts with `pk_` — and store it somewhere safe.
  </Step>
</Steps>

<Callout type="warn">
  The API token carries the creating user's full access to every workspace they belong to. Treat it like a password — do not commit it to source control or share it publicly. Sim encrypts the token at rest.
</Callout>

## Adding the API token to Sim [#adding-the-api-token-to-sim]

<Steps>
  <Step>
    Open **Integrations** from your workspace sidebar
  </Step>

  <Step>
    Search for "ClickUp" and open it, then click **Add to Sim** and choose **Add API token**
  </Step>

  <Step>
    Paste the API token (`pk_...`) and optionally set a display name and description
  </Step>

  <Step>
    Click **Add API token**. Sim verifies the token by fetching the authorized user from ClickUp — if it fails, you'll see a specific error explaining what went wrong.
  </Step>
</Steps>

## Using the credential in workflows [#using-the-credential-in-workflows]

Add a ClickUp block to your workflow. In the credential dropdown, select the saved ClickUp API token. Choose the operation and configure its inputs.
The block calls the ClickUp API (`api.clickup.com`) with the token. Everything the workflow does — creating tasks, adding comments, uploading attachments — is attributed to the user who created the token.

## Verify access and rotate the token [#verify-access-and-rotate-the-token]

Run **Get Workspaces** to inspect accessible workspaces, then test the task, comment, attachment, or other action your workflow needs. Removing the issuing user's workspace access removes the token's access to that workspace; account deactivation can prevent workflows from authenticating. A dedicated integration user still needs active membership and permissions.

[Personal API tokens do not expire](https://developer.clickup.com/docs/authentication). To rotate one, select **Regenerate** under **Settings → Apps → API Token**, then update the saved credential in Sim. Regeneration immediately invalidates the old value, including in other integrations that use it.