ClickUp integration

Connecting ClickUp lets Causentrix file an incident's root-cause analysis — and each individual remediation action within it — as ClickUp tasks, then update those actions as the tasks move through your list. It works the same way the Jira integration does; only the connect form and the destination picker differ.

Before you start

• A ClickUp account for Causentrix to act as. Every task is created as this account, with exactly its permissions. Use a dedicated service account rather than your own login — otherwise the integration breaks when that person's access changes.
• A personal API token for that account. Signed in as that account, open ClickUp's Settings and pick ClickUp API from the sidebar (under Integrations & ClickApps), then the API tokens tab. Select Generate to create the token, or Copy if one already exists — the field only ever shows the token masked, so copy it now. The token starts with pk_. Where the button reads Regenerate, the account already has a token and pressing it invalidates the old one everywhere it is used, so copy rather than regenerate unless you mean to rotate it.
• A List to file into, with the service account able to see the Space it lives in and create tasks in it.

In Causentrix you need the manage integrations capability — org owners have it by default.

1. Connect

Go to Integrations, press Connect on the ClickUp card, and paste the token. There is no site URL or account email to supply: ClickUp has one host, and the token carries its own identity. Press Test connection to confirm which account it belongs to before saving. The token is encrypted before storage.

Unlike a Jira API token, a ClickUp personal token does not expire and there is no refresh cycle. That is convenient and it is also the reason to treat it carefully — it stays valid until someone revokes it. Disconnecting here forgets it; regenerating in ClickUp invalidates it everywhere.

2. Choose a Space, then a List

A ClickUp task lives in a List, which lives in a Space (and possibly a Folder), so the destination takes two picks rather than Jira's one. Choose the Space first; the List dropdown then shows every list in it, with the folder as a path prefix such as Sprints / Sprint 24. Folderless lists appear without a prefix.

Changing the Space clears the List, because a list from another Space would make every filing attempt fail. Task type is usually just Task — other types exist only on plans with Custom Task Types.

3. Map your statuses

ClickUp statuses are defined per List, so Causentrix reads the ones your chosen list actually uses and asks you to say what each means in its own terms: Open, In progress, Resolved or Dismissed. Anything left as Not mapped is deliberately ignored — a task moving into it leaves the remediation action untouched. Press Save mapping when you're done.

4. Turn on write-back and file a task

A new connection is read-only. Switch on Allow write-back, and once a Space, List and task type are all chosen, each remediation action on an incident gains a + ClickUp button, with + ClickUp RCA in the panel header for the whole analysis.

What Causentrix puts in a task

• Name — the remediation action in its own words.
• Description — markdown: the supporting evidence, the causal-chain step it addresses, the implicated file and line where Causentrix grounded it in real code, and a link back to the incident.
• Priority — ClickUp's Urgent / High / Normal / Low.
• Tags — causentrix on every task, plus one for the incident and one for the remediation tier. Filter your list on causentrix to see everything this integration has created.

ClickUp lowercases tags, and the causentrix tag is also how status sync finds its tasks — removing it from a task stops that task syncing.

Rate limits

ClickUp allows 100 requests per minute per token on Free, Unlimited and Business plans (1,000 on Business Plus, 10,000 on Enterprise). Causentrix polls one list rather than your whole workspace and caches the Space and List options, so normal use stays well inside that. If you do hit it, the card says so and names roughly when it clears; the next sync recovers on its own.

If something goes wrong

• "ClickUp rejected the credentials" — the token was regenerated or revoked, or that account can't see this workspace. Reconnect with a fresh token.
• The List dropdown is empty — the service account can't see any list in that Space, or every list in it is archived.
• No ticket buttons on an incident — write-back is off, the destination isn't fully chosen, or your account lacks manage integrations.
• Tasks file but statuses never change — the status they're moving into isn't mapped, or automatic sync is switched off.

Disconnecting

Disconnect deletes the stored token and Causentrix's record of which task belongs to which action. The tasks themselves stay in ClickUp untouched, but reconnecting later will not re-adopt them.