Skip to main content

Documentation Index

Fetch the complete documentation index at: https://support.configview.com/llms.txt

Use this file to discover all available pages before exploring further.

ConfigView pulls ClickUp data through one Personal API Token. The token has access to every workspace your ClickUp user is a member of — so the inventory follows your user’s membership, not a per-workspace install. You will end up with 1 secret in ConfigView (CLICKUP_TOKEN) when setup is complete.

⚠️ Required: token must be generated by a Workspace Admin or Owner

ClickUp’s Personal API Token inherits the generating user’s permissions. ConfigView requires the token to come from a Workspace Admin or Owner — not a regular member, not a guest. If you use a member-level token:
  • Private spaces the member cannot see will be missing from the inventory entirely
  • Webhooks returns empty
  • Workspace Seats returns null seat counts
  • Custom Roles admin-only fields are blank
  • Other admin-gated data is silently dropped without an error
If the customer doesn’t have an Admin available, ask them to either (a) elevate an existing user temporarily, or (b) create a dedicated service user, promote it to Admin, then generate the token from that account. Don’t proceed with a member-tier token — the data gaps will look like bugs later.

Step 1: Generate the Personal API Token

  1. Sign in to ClickUp as a Workspace Admin or Owner (see the requirement callout above — this is not optional)
  2. Verify your role: click your profile avatar (bottom-left) → SettingsMy SettingsPeople (or look at the workspace member list). Your role next to your name must read Admin or Owner. If it reads Member or Guest, stop and follow the workaround in the callout above.
  3. From Settings, in the left sidebar under My Settings, click Apps
  4. Under API Token, click Generate (or Regenerate if one already exists)
  5. Copy the token (starts with pk_). You can re-view it any time from this page, but treat it like a password.
OAuth alternative. ClickUp also supports OAuth for multi-tenant apps. ConfigView is single-tenant per satellite, so the Personal API Token is the right choice — simpler and works on every plan tier.

Step 2: Add the secret to ConfigView

  1. Go to your ConfigView dashboard: https://{companyname}.configview.com/admin/secret/
  2. Click Add Secret
  3. Secret name: CLICKUP_TOKEN
  4. Secret value: Paste the pk_... token from Step 1
  5. Click Save

Step 3: Enable the ClickUp scripts

  1. Go to: https://{companyname}.configview.com/admin/cron/
  2. You should see clickup in the list of available apps
  3. Select scripts to enable. Parents must be enabled before children — ConfigView wires the dependencies automatically, but the load order matters for first-run timing:

Identity & governance

ScriptNotes
WorkspacesAll workspaces your user belongs to. Most other scripts depend on this list.
Workspace PlanCurrent plan (Free Forever / Unlimited / Business / Business Plus / Enterprise) per workspace. Depends on Workspaces.
Workspace SeatsUsed vs. total member + guest seats. Useful for billing reconciliation. Depends on Workspaces.
Groups (User Groups)Workspace-defined user groups (e.g. “Engineering”, “Design”). Depends on Workspaces.
Custom RolesCustom role definitions + how many members hold each. Depends on Workspaces. Enterprise-only feature.
WebhooksActive webhooks at the workspace level with their health status (active / failing). Admin-only. Depends on Workspaces.
Workspace Custom FieldsCustom field definitions reusable across the workspace. Depends on Workspaces.
Custom Task TypesUser-defined task types beyond the built-in “Task” (e.g. “Bug”, “Story”). Depends on Workspaces. Business+ feature.

Hierarchy (Space → Folder → List)

ScriptNotes
SpacesAll spaces in each workspace, both active and archived. Depends on Workspaces.
Space TagsTag definitions per space. Depends on Spaces.
FoldersAll folders in each active space, both active and archived. Depends on Spaces.
Lists (in Folders)All lists nested under each folder. Depends on Folders.
Folderless ListsLists that sit directly under a Space (no folder). Depends on Spaces.
List MembersWho has access to each list. Depends on Lists + Folderless Lists. Combines both list sources.

Tasks & activity

ScriptNotes
TasksEvery task across every active list, paginated. Depends on Lists + Folderless Lists. Includes subtasks and closed tasks. Largest table — can be hundreds of thousands of rows for active workspaces.
Time Entries (Last 30 Days)Time tracked across the workspace in the last 30 days. Depends on Workspaces. Cumulative history accumulates from successive runs.
GoalsGoals + their key results. Depends on Workspaces. Includes completed goals.
  1. Click Save
Scoping tip. If you’re rolling out ClickUp ingestion to a workspace with tens of thousands of tasks, enable the Identity and Hierarchy tiers first, verify the row counts look right, then turn on Tasks. The Tasks endpoint paginates 100 rows per request, so a 50k-task workspace is ~500 API calls — well within ClickUp’s per-token rate limit (100 req/min) but takes ~5 minutes per full sync.

Step 4: Verify

  1. Go to: https://{companyname}.configview.com/admin/status/
  2. Run the ClickUp health check
  3. At minimum Workspaces should return a non-zero row count matching the workspaces your user is in
If a check fails:
  • 401 Token invalid — Token was regenerated or revoked. Re-generate from Step 1 and update CLICKUP_TOKEN.
  • Workspace Seats returns null or zero values — Token’s user is not a Workspace Admin. This is the canary symptom of a member-tier token; re-generate from an Admin/Owner account per Step 1. Do not “accept” this and move on — other endpoints are silently dropping admin-gated data too.
  • Webhooks returns zero rows — Same root cause as the Seats issue. Member-tier tokens see no webhooks. Re-generate from Admin.
  • Private spaces missing from Spaces — Same root cause. Member-tier tokens are blind to spaces they’re not invited to. Re-generate from Admin.
  • Tasks running slowly — Expected for big workspaces. ClickUp’s rate limit is 100 req/min per token; the script paces itself but a 100k-task workspace takes 15-20 minutes. Schedule it daily (or less frequent) rather than hourly.
  • Custom Roles or Custom Task Types returns empty — Feature requires Business+ / Enterprise plan respectively. Empty is the correct answer if you’re on a lower tier.

Data Tables

All tables include a run_at column for historical tracking. Selected highlights below.
TableSourceKey Columns
clickup_workspacesGET /teamworkspace_id, name, color, members_count
clickup_workspace_planGET /team/{id}/planworkspace_id, plan_name, plan_id
clickup_workspace_seatsGET /team/{id}/seatsworkspace_id, filled_member_seats, total_member_seats, filled_guest_seats
clickup_groupsGET /team/{id}/groupgroup_id, name, handle, member_count, members_json
clickup_custom_rolesGET /team/{id}/customrolesrole_id, name, inherited_role, members_count
clickup_webhooksGET /team/{id}/webhookwebhook_id, endpoint, events_json, health_status, health_fail_count
clickup_spacesGET /team/{id}/spacespace_id, name, private, archived, features_json
clickup_foldersGET /space/{id}/folderfolder_id, space_id, name, task_count, archived, lists_json
clickup_listsGET /folder/{id}/listlist_id, folder_id, name, task_count, due_date, archived
clickup_folderless_listsGET /space/{id}/listlist_id, space_id, name, task_count, due_date, archived
clickup_list_membersGET /list/{id}/memberlist_id, user_id, username, email, role, custom_role_id
clickup_tasksGET /list/{id}/task (paginated)task_id, list_id, name, status, assignees_json, priority, due_date, time_estimate, time_spent, custom_fields_json
clickup_time_entriesGET /team/{id}/time_entriestime_entry_id, task_id, user_id, billable, start_time, duration_ms
clickup_goalsGET /team/{id}/goalgoal_id, name, percent_completed, owners_json, key_results_json

What you can’t ingest with this setup

  • Task Comments. Comments are fetched per-task (GET /task/{id}/comment), which means one API call per task. For workspaces of any meaningful size this exceeds the 100 req/min rate limit on a useful cadence. Open a feature request if you need it — we’d ship it as a separate opt-in script with a “last edited” cap.
  • Attachments. Same per-task fan-out problem. Out of scope.
  • Chat messages / view comments. Out of scope; covered by Slack/Teams ingestion if that’s where the conversation actually happens.
  • Views (Kanban / Gantt / Calendar configurations). Not in this version. Easy to add if it matters — request the Views endpoint family.
  • Documents (ClickUp Docs). Separate API surface that’s still in beta; not in this version.