ClickUp

ClickUp's authorisation works differently to the other trackers we connect to, and it is worth knowing before you press Connect rather than after. ClickUp has no permission scopes at all: you choose which Workspaces to authorise on its consent screen, and the connection then has the same access in those workspaces as the person who authorised it. There is no read-only option to ask for.

1. 1In the Lineman dashboard, open Integrations and choose ClickUp, or go straight to /dashboard/integrations/clickup.
2. 2Press Connect. ClickUp asks you to authorise Lineman against one or more workspaces, and you are returned to the integration page once you approve. Lineman tracks one workspace, so if you authorise several it will tell you which one it took.
3. 3There is nothing to install in your repositories and no custom field to add to your tasks. Lineman writes one comment per task and nothing else.
4. 4Enable at least one Space. The integration page lists the Spaces in your workspace, all switched off. Nothing is written to any task until you switch one on, because Lineman comments on your tasks and that should be your decision rather than a side effect of connecting. Costs start appearing on the next scheduled run after that.

Attribution is entirely by branch name. Lineman looks for a ClickUp task id in the name of the branch the AI work happened on, and adds the cost of that work to that task. There is no manual linking step and no task picker, so a branch that does not name a task cannot be attributed to one.

A Custom Task ID such as DEV-123 is indistinguishable from a Jira project key or a Linear team key, so Lineman will not assume one is ClickUp's. Left alone, it only recognises the two unambiguous forms, CU-abc123 and #abc123.

• Declare your prefixes. Add your ClickUp prefixes to your ticket-key settings. Until you do, branches named with a Custom Task ID are not attributed to ClickUp, and a Jira or Linear key of the same shape is never mistaken for one.
• Every match is confirmed with ClickUp. Even for a declared prefix, Lineman asks ClickUp whether the key is a real task in your workspace before it writes anything, so a key that belongs to another tracker is left alone rather than guessed at.

The cost lands as a comment on the task, reading AI spend on this task: $12.40. ClickUp offers no way for an application to create a custom field, so a field-based figure would mean every customer hand-creating a field on every List before anything happened. A comment works the moment you tick a Space.

• Updates replace, they do not stack. However many times the total changes, the task keeps one Lineman comment showing the latest figure, edited in place.
• Nobody is notified. The comment is written and updated without notifying watchers, so a task does not generate alerts every time the running total moves.
• It is the whole task, not you. The figure covers everyone who worked on the linked branch, so two people on the same branch produce one combined number rather than one each.

• Amounts are in US dollars. Lineman shows money in dollars everywhere, never cents, so the comment can be compared directly with what you see in Cost Explorer.
• It is cumulative. The figure is everything spent on the linked branch so far, not the cost of the last session, so it only rises while work on the task continues.
• It is not instant. The comment is refreshed on a scheduled run, and only when the total has actually changed, so cost recorded a few minutes ago will not be on the task yet.

Disconnecting in Lineman deletes the stored token and stops all writing. ClickUp publishes no way for an application to revoke its own authorisation, so the grant itself stays listed in ClickUp until you remove Lineman there as well. Comments already on your tasks are left where they are; delete them in ClickUp if you want them gone.

• Check a Space is switched on. A freshly connected workspace has every Space switched off, so nothing is written anywhere until you enable one. This is the most likely reason a new connection looks like it is doing nothing.
• Check the branch name. No task id in the branch name means no attribution, and this is by far the most common cause.
• Check your Custom Task ID prefixes are declared. A branch named DEV-123 is not treated as ClickUp's until you say the DEV prefix is yours, because it looks exactly like a Jira or Linear key.
• Check the connection is not asking to be reconnected. A ClickUp token does not expire, so if ClickUp stops accepting it the authorisation has been removed at ClickUp's end. The integration page says so plainly, and reconnecting is the only fix.
• Check there is spend to show. A task whose branch has recorded no AI cost gets no comment at all, rather than a comment reading zero.
• Check what the connect button says. If it reports that ClickUp is not configured, the OAuth application has not been registered for your environment and connecting cannot succeed until it is.