Open Linear issues from Yocoolab feedback
Every new comment thread on a mapped repository opens a Linear issue. Status stays in step once you add the webhook.
Availability, October 2026
Overview
Once a repository is mapped to a Linear team, each new Yocoolab thread on it opens a Linear issue automatically; there is no separate send step. The issue description has the comment, the element’s selector, a link to the page and, when one is recorded, the pull request link. It does not include the screenshot.
- Replies: messages added in Yocoolab are posted to the issue as comments. Linear comments do not come back.
- Status: resolving the thread in Yocoolab updates the issue, and with the webhook below, completing the issue in Linear resolves the thread.
Prerequisites
- A Linear workspace
- Permission to create API keys in Linear settings
Setup Steps
- 1
Create a Linear API key
In Linear, go to Settings → API → Personal API Keys and click Create Key.
Copy the key — you won't be able to see it again.
- 2
Open Yocoolab integration settings
In the admin dashboard, go to Settings → Integrations → Linear.
- 3
Enter your Linear API key
Paste the API key and click Save. Yocoolab validates the key by querying the Linear GraphQL API.
- 4
Test the connection
Click Test Connection. You should see your Linear user name and workspace.
- 5
Map repositories to Linear teams
For each Yocoolab repository, select a Linear team. New threads on that repository open issues in the mapped team.
Note
The list shows only repositories connected to your workspace, and connecting repositories is currently unavailable, so a workspace created today has nothing to choose here.
- 6
Set up a webhook (optional)
For Linear status changes to reach Yocoolab, register a webhook. After you save your API key, Yocoolab shows a webhook URL for your workspace. It looks like this and includes your workspace’s secret, so keep it private:
https://<yocoolab-backend>/webhooks/linear?secret=<your workspace secret>In Linear, go to Settings → API → Webhooks, create a webhook with that URL, and select the Issues resource with the Update action.
Verification
Pin a test comment on a page in a mapped repository. A Linear issue should appear in the mapped team with the comment, the element’s selector and a link to the page.
Reference
API endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /api/v1/linear/config | Save Linear API key |
GET | /api/v1/linear/config | Get current Linear configuration status |
GET | /api/v1/linear/test | Test stored Linear credentials |
GET | /api/v1/linear/teams | List accessible Linear teams |
POST | /api/v1/linear/mappings | Create or update a repo-to-team mapping |
GET | /api/v1/linear/mappings | List all repo-to-team mappings |
DELETE | /api/v1/linear/config | Disconnect Linear integration |
Troubleshooting
Warning
Invalid API key — Linear API keys are long alphanumeric strings starting with lin_api_. Make sure you copied the full key.
Note
Team not found — The API key must belong to a user who is a member of the team you want to map. Check your Linear team membership.
Ready to start reviewing on the real product?
Install the free extension for Chrome, Edge or Firefox and pin your first comment on a live page.
No seat fees in beta. Every team member included — designers, developers, PMs, stakeholders.