How to connect Linear to Layerdock
Once Linear is connected, every new pin left on your site becomes an issue in the team you choose, with the reviewer's comment as the description and the screenshot, page URL, CSS selector, viewport and browser already attached. Setup takes about two minutes and needs no developer.
Before you start
A Linear account that can create issues in the team you want, and edit access to the Layerdock dock, on a plan that includes integrations.
Connect it
1. Open the Linear page
In Layerdock, go to Integrations in the sidebar and click Linear. You can also do this from inside a dock, under Settings → Integrations.
2. Connect a dock
Click Connect a dock, choose which dock this is for, then Continue to Linear. Linear asks you to authorise Layerdock for read and write access. Approve it and you come straight back.
3. Pick a team
The first team is selected automatically so it works immediately. If that is not the right one, use the dropdown on the dock's row to change it. Switching teams touches only the routing; it never re-authorises or changes the stored token.
4. Test
Click Test. An issue should appear in the team within a few seconds. Then leave a real pin on your site to see the full format.
What the issue contains
The comment as the description, the screenshot embedded inline, the page URL, element label, CSS selector, viewport and reporter, the browser and OS, and a link back to the pin in Layerdock.
Two-way sync
To have Linear statuses flow back — moving an issue to Done marks the pin resolved — add a webhook in Linear:
- Linear → Settings → API → Webhooks → New webhook
- URL:
https://www.layerdock.io/api/webhooks/linear - Enable the Issues event, and only that one
- Copy the signing secret to whoever manages your Layerdock deployment; it goes in
LINEAR_WEBHOOK_SECRET
Layerdock reads Linear's stable state category rather than the display name, so a custom workflow still works: completed resolves the pin, started moves it to in progress, canceled closes it. A state it does not recognise is ignored, never guessed at.
Tick only Issues. Other event types are verified, parsed and thrown away, and the endpoint is rate limited per source IP — which every Linear customer shares — so noise from one workspace can cost another a real status change.
Good to know
Only new pins create issues. Replies and status changes do not update an existing issue; that is what two-way sync covers, in the other direction.
Deleting a team in Linear does not break the connection.Layerdock falls back to the team's default workflow state and records a warning rather than dropping the issue.
Linear returns HTTP 200 even when a mutation fails, with the problem in an errors array. Layerdock checks that array rather than the status code, which is why a failed create shows up as a failed delivery instead of silently vanishing.
If it stops working
Reconnect needed means the authorisation was revoked in Linear. Click Reconnecton that dock's row.
Prefer a chat channel to an issue tracker? Connect Slack instead, or see all documentation.