How to connect ClickUp to Layerdock
Once ClickUp is connected, every new pin becomes a task in the list you choose, with the screenshot embedded and the page, element, viewport and reporter's browser in the description.
Before you start
A ClickUp account that can create tasks in the list you want. Nothing to install.
Connect it
1. Authorise
In Layerdock, go to Integrations → ClickUp → Connect a dock, choose the dock, then Continue to ClickUp. ClickUp asks which Workspaces to authorise. Approve, and you come back.
2. Pick a list
Click Choose a liston the dock's row. Lists are grouped by Space, because names repeat across Spaces.
ClickUp connects switched off until you do this.There is no sensible default list, and guessing one would drop your client's feedback somewhere nobody is looking.
3. Test
Click Test. A task should appear within a few seconds, tagged layerdock.
Good to know
The picker shows the first ten Spaces.Both foldered and folderless lists are included — those are two separate endpoints in ClickUp, and a picker that queried only one would silently hide half the Workspace. The limit is deliberate: a picker that spends thirty seconds enumerating an enterprise Workspace is not useful.
Archived lists are hidden. ClickUp keeps them addressable by id, so a task created into one succeeds and is then invisible wherever you are looking.
The screenshot is embedded by URL, not uploaded. A second multipart upload is another thing that can fail, and a task whose image quietly vanished is worse than one carrying a link that always renders.
The authorisation does not expire. ClickUp access tokens have no lifetime, so there is nothing to refresh; only a revocation ends a connection.
ClickUp is outbound only. Closing a task will not resolve the pin. Linear, GitHub and Jira sync both ways.
If it stops working
Reconnect needed means the token was revoked in ClickUp. Click Reconnecton that dock's row.
“That ClickUp list no longer exists” means the list was deleted. Pick a new one; no retry can find a list that is gone.
“Could not be verified, start again”during authorisation is deliberate. ClickUp echoes back a security parameter Layerdock sends, and if it comes back missing or altered the connection is refused rather than trusted — otherwise someone could hand you a link that wired their ClickUp Workspace to your dock.
Want statuses to flow back as well? Linear, GitHub and Jira all sync both ways. See all documentation.