Reference · Credentials
ClickUp API credentials
Used by 2 BusyBot nodes.
clickupApi 1 field The ClickUp credential holds a personal API token from your ClickUp account. It acts as your user, so it reaches every workspace, space and task your account can access — which is usually broader than a single workflow needs.
Fields
| Field | Type | Required | Notes |
|---|---|---|---|
Access TokenaccessToken | password | Yes | Your ClickUp personal API token. |
Getting your credentials
- Sign in to ClickUp.
- Open your personal settings and find the Apps section.
- Generate a personal API token and copy it.
- Paste it into the credential’s Access Token field in BusyBot.
Permissions and scopes
The token carries your own permissions across every workspace you belong to. For shared automation, consider generating it from a dedicated account added only to the relevant spaces.
Troubleshooting
- 401 Unauthorized — the token is wrong or was regenerated in ClickUp.
- Team or space not found — the account behind the token is not a member of it, or the ID is wrong.
- Actions attributed to you — the token acts as its creator; use a dedicated account if that matters.
Frequently asked questions
Where is the token generated?
In your personal ClickUp settings under Apps, rather than at the workspace level.
Does it cover every workspace I belong to?
Yes — a personal token carries your access across all of them, which is broader than many automations need.
Does one token cover the ClickUp node and its trigger?
Yes, both declare the same credential type.
Nodes that use ClickUp API
One credential works across every node below — create it once and reuse it.
Last updated . Spotted something wrong? Tell us.