Screendog files Linear issues directly via the GraphQL API.
Connect Linear once with a personal API key. Every recording becomes a fully-structured Linear issue — title, description, repro, embedded video link — created server-side via Linear's `issueCreate` mutation.
| Capability | Status |
|---|---|
| Live API integration | Yes — GraphQL `issueCreate` |
| Auto-resolves first team if `teamId` blank | Yes |
| Credentials stored per workspace | Yes — never returned to the browser |
| Workspace owner / admin can connect | Yes; role-gated |
| Two-way sync (status updates back into Screendog) | No — file-and-forget by design |
How it works
In `/<workspace>/settings`, paste your Linear personal API key (`lin_api_…`). Optionally specify a team ID; if blank, Screendog uses your first team. When you finish a recording, click File to Linear — Screendog calls the GraphQL endpoint server-side, attaches the share URL, and returns the new issue's URL.
What lands in Linear
Title, description (markdown), repro steps, expected/actual, severity, browser/OS metadata, recording share link, transcript excerpt. The full transcript stays on Screendog (linked) so the issue body stays readable.
Security model
Your API key is stored only in the workspace's `tenant_integrations` row. List endpoints expose `configured: true` plus a non-sensitive hint (team ID prefix); the raw key is never returned over the wire.
Frequently asked
Does Screendog need access to my whole Linear workspace?
It needs whatever scopes your personal API key grants — typically issue-create for the chosen team.
Can I file to multiple teams?
Today the integration files to one team per Screendog workspace. For multi-team filing, create separate Screendog workspaces.
Will Linear close the loop back to Screendog?
No two-way sync today. Status changes happen in Linear; Screendog records the URL of the issue you filed.
Try Screendog free.
5 recordings on the free trial. Real Linear, GitHub, Notion, Slack, and Jira filing. No credit card.
Start a workspace — free