Connect ClickUp

ddx PMO reads your ClickUp as a process signal — how work actually moves — not as a copy of your tasks. ClickUp tasks never become register items; instead their status history powers the Flow view: rework, ageing tasks, cycle time, and lead time. See Flow in the glossary.

You set ClickUp up per project under Settings → Connections.

Connect the workspace

Connecting the workspace is done once per workspace by an org admin.

1. In ClickUp, open Settings → Apps and copy a personal API token (it starts with pk_).
2. In ddx PMO, go to Settings → Connections and paste the token into the Tracker (ClickUp) section.
3. If the token can see more than one ClickUp workspace, also enter the Workspace ID — otherwise ddx PMO can’t tell which one you mean.
4. Choose Connect. The token is checked against ClickUp and stored encrypted.

One ClickUp workspace connects per ddx PMO workspace, and every project binds against that same connection.

Bind a container

ClickUp has no native “project”, so you bind a space, folder, or list — whichever level matches how the client organises ClickUp. You can bind more than one if the project spans several.

1. In the Tracker section, choose Add container….
2. Drill down from space to folder to list. Each row shows its ID and a ClickUp ↗ link so you can confirm you’ve got the right one before binding — same-named siblings look identical otherwise.
3. Choose Bind, then Confirm bind.

A bound container appears in the table with its sync status: not synced, synced, paused, or error.

Run the backfill

After you bind a container, choose backfill now on its row. The backfill pulls the container’s tasks, seeds the per-status timings the Flow view needs, and registers the ClickUp webhook so future status changes stream in automatically.

Caution

Don’t create the webhook by hand in ClickUp — the app manages it for you, and a hand-made one won’t work with ddx PMO. If the webhook ever stops, just run the backfill again to re-register it.

Note

Webhook registration only happens when the deployment’s public URL is configured. If the backfill reports that webhook registration was skipped, ask whoever runs your deployment to set it; the backfill itself still works, and re-running it once the URL is set registers the webhook.

Manage a binding

Each bound container has its own controls:

Action	What it does
re-backfill	Pulls the container again and re-checks the webhook.
pause / resume	Stops or restarts syncing without losing data.
unbind	Stops syncing; already-derived flow signal stays.
unbind & delete data	Permanently removes this container’s tracked cases, flow history, and any ClickUp-comment sentiment. The raw ClickUp data is untouched, so re-binding and re-running the backfill rebuilds it.

Where the result shows up

Flow signal lands on the project’s Flow page. ClickUp is managed as a module, so you can turn it off under Settings → Modules; that keeps existing data but stops new syncing.