Map your ClickUp workspace in 15 minutes

Step 1. Get credentials (2 min)

1. ClickUp → Settings → Apps → API Token
2. Note your Team ID (Workspace ID): app.clickup.com/{team_id}/… or Settings → Workspace

Step 2. Minimal config (3 min)

provider: clickup

clickup:
  token: ""
  workspace: "12345678"

teams:
  - name: Growth
    clickup:
      list_id: "901234567890"

metrics:
  clickup:
    workflow:
      cycle_start_statuses: [in progress]
      lead_end_statuses: [complete]
    ftpr:
      fail_tags: [ftpr-fail]
    bugs:
      tags: [bug]
      title_prefix: "BUG |"

Step 3. FTPR automations (5 min)

ClickUp FTPR is tag-based. Create a tag (e.g. ftpr-fail) and an automation:

When status moves backward (e.g. Complete → In Progress), add tag ftpr-fail

Set metrics.clickup.ftpr.fail_tags to match. Without fail tags, FTPR shows n/a (not 0%).

Step 4. Multi-squad routing (optional)

Use this when two or more squads share the same ClickUp folder or list.

1. Create a custom dropdown in ClickUp (for example Squad) with one option per squad.
2. In config.yml:

metrics:
  clickup:
    routing:
      use_squad_field: true
      squad_field: Squad
      # squad_field_by_space:   # when the dropdown label differs per space
      #   "12345678": Team

teams:
  - name: Platform
    clickup:
      folder_id: "16615923"
      routing:
        squad_value: Platform
  - name: Results
    clickup:
      folder_id: "16615923"
      routing:
        squad_value: Results

Pulse routes by list, folder, tags, and locations first. The dropdown only breaks ties when multiple squads match the same list or folder. If a list belongs to one squad only (list_ids), routing does not need the dropdown.

Full key reference: ClickUp configuration.

Step 5. Config audit + spot-check

First load on large workspaces can take 2–5 minutes. Refresh within 5 minutes uses cache.