Findings become Linear issues, evidence attached.
Connect once, pick a team, and approved findings arrive as Linear issues with priority set from severity, the verbatim quote, and a link to the moment. Two minutes of setup.
Five steps.
After step 4, every member can push; viewers stay read-only.
- STEP 01
Open the integrations settings
Settings, then Integrations under Push destinations. Connecting needs a workspace admin or owner.
- STEP 02
Connect Linear
On the Linear card, choose Connect and sign in to Linear, approving read, write, and issue-creation access - listed in the dialog before you approve. Prefer a key? The dialog also accepts a personal API key plus your team ID; Linear lists both in its settings, and the dialog links there.
- STEP 03
Pick the team
The destination picker lists your Linear teams live. Pick the one findings should land in. Issues are created in that team and never silently moved.
- STEP 04
Confirm the card reads connected
The Linear card shows the connected workspace and the chosen team. A pasted key is checked with Linear before it is saved, so mistakes surface in the dialog, not on the first push.
- STEP 05
Push an approved finding
Approve a finding on any recording, choose Push, and pick Linear. The app confirms "Queued"; Integration activity shows the delivery through to the created issue, linked by its identifier.
The field mapping, exactly.
The finding title.
Severity maps to Linear priority: critical to Urgent, high to High, medium to Medium, low to Low; findings without severity arrive as No priority.
The finding description, the verbatim evidence quote as a blockquote, and a link that opens the recording at the second the evidence occurred - all in Markdown, the way Linear likes it.
The team you picked at setup. Re-pushing updates the issue in place and never moves it between teams.
Delivery is queued with automatic retries; failures appear in Integration activity with a Retry button that can never duplicate an issue. If the card ever shows "Reconnect needed", reconnect from the card - the chosen team is kept. More states: troubleshooting.
Linear integration, answered.
- A paid Citesvue plan to push (connecting works on every plan), the workspace admin role in Citesvue, and a Linear account that can create issues in the target team.
- Linear Settings, under API: create a personal API key there, and your team ID is listed on the same screen. The connect dialog links straight to it. Issues created with a personal key are attributed to that Linear account.
- Citesvue remembers the issue it created and updates it in place. The push dialog shows the existing identifier, and the button reads "Push again".
- No - Linear, like Jira, takes one finding per issue by design, so every issue in the tracker is one someone chose to file. For batch delivery use Notion or Slack.
- Citesvue forgets the credential and stops sending; issues already created stay in Linear, and delivery history remains visible. Reconnect any time - and re-push anything that had failed rather than retrying it.
Your next recording could be
your most
valuable asset.
Or it could sit in a Drive folder nobody opens again. The difference is whether it has citations attached.
- SetupOne drag-and-drop upload, or send the notetaker. No plugins.
- First insightCited Q&A on a 60-min recording in under 6 minutes.
- Cancel anytimeFull data export, full right to erasure.