Citesvue does not want to be your next ticket system, wiki, or chat tool. It wants to be the evidence source those tools were missing. Five native connectors, a generic webhook, and a REST API cover the last mile.
Empty cells are worse than honest gaps. Every row below is filled in — including the “coming” work flagged inline.
| Destination | Artifact types | Payload includes | Sync | Auth |
|---|---|---|---|---|
| Jira | Bugs · action items · requirements | Full quote · frame · severity → priority · component | 1-way (2-way: coming) | OAuth 2.0 / API token |
| Linear | Bugs · feature requests · action items | Quote · frame · severity → priority · labels | 1-way | OAuth 2.0 |
| Notion | Requirements · decisions · findings packs | Cited block / database row · evidence appendix | 1-way | OAuth 2.0 |
| Confluence | Decisions · approvals · audit reports | Macro with citation · versioned | 1-way | OAuth 2.0 / Atlassian token |
| Slack | Per-channel digest · severity-routed notifications | Artifact summary · quote · deep link | Push only | OAuth 2.0 |
| Webhook | Any artifact type, configurable per workspace | Versioned JSON · HMAC signed · retry w/ backoff | Push only | Workspace secret |
| REST API | Recordings, transcripts, frames, artifacts, Q&A | Same shape as UI · paginated · OpenAPI spec | Read + write | Scoped API keys |
Bug and action-item artifacts push as issues with the quote in the description, the frame embedded, the timestamp linked back to Citesvue, and severity mapped to Jira priority. Projects, issue types, and custom fields are configurable per workspace. Two-way status sync — issue state flowing back into the artifact review state — is on the roadmap.
Same shape as Jira, tuned for Linear’s issue model and cycles. Artifacts map to issues with labels for artifact type; severity maps to priority; the originating recording is linked in the issue description with a deep link to the exact timestamp.
Targeted at requirements, decisions, and findings packs. A pushed artifact becomes a Notion database row or page block under a configurable parent. Decisions can flow into a project decision log; requirements into a PRD template; findings into a client-ready deliverable.
Tuned for the decision-heavy, audit-heavy workflows common in enterprise. Decisions and approvals push as structured macros under a configurable space and parent page. Audit trail is preserved in Confluence’s native versioning.
Real-time notifications and digests with per-channel rules: critical bugs here, approvals there, end-of-day digest for everything else. Each Slack message carries the artifact summary, the originating quote, and a deep link back to the timestamp — not just a ticket URL.
For everything else. Webhooks: configurable per artifact type, HMAC-signed deliveries, retries with exponential backoff, full delivery logs. REST API: every object the UI exposes — recordings, transcripts, frames, artifacts, Q&A responses — available with scoped API keys, paginated, versioned, and OpenAPI-documented.
Destination credentials are encrypted at rest per workspace, scoped, rotatable, revocable. Push actions respect both the Citesvue role model and the destination’s own permissions. If the user can’t create a Jira issue in the target project, the push fails cleanly with a clear error — never silently.
Non-negotiable. Every artifact that leaves Citesvue carries the same six things — wherever it lands.
Type, severity, structured fields.
Exact words that triggered the artifact.
Who said it.
Deep link back to the moment in Citesvue.
Embedded or linked, depending on destination.
Identifiers that let a reader retrace the chain.
Full export of every artifact, transcript, and frame index in CSV, JSON, and DOCX. Account-level deletion is honoured end-to-end with a signed receipt. Webhooks and REST mean the evidence layer is portable — nothing is trapped in the UI.
Or it could sit in a Drive folder nobody opens again. The difference is whether it has citations attached.