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. Four native connectors and a signed generic webhook cover the last mile.
Empty cells are worse than honest gaps. Every row below describes a connector that ships today; missing tools live on the roadmap, not in this table.
| Destination | Artifact types | Payload includes | Sync | Auth |
|---|---|---|---|---|
| Jira | Bugs · action items · requirements | Title · description · severity · evidence quote | 1-way push | Jira email + API token, per workspace |
| Linear | Bugs · feature requests · action items | Title · description · severity · evidence quote | 1-way push | Linear API key, per workspace |
| Notion | Requirements · decisions · findings | Database row with evidence fields | 1-way push | Notion API key + database, per workspace |
| Slack | Artifact notifications to a channel | Artifact summary · evidence quote | Push only | Incoming webhook URL, per workspace |
| Webhook | Any artifact selection | JSON · HMAC-SHA256 signed when a secret is set | Push only | Your endpoint URL + optional signing secret |
Bug and action-item artifacts push as issues in your configured project: the artifact title becomes the summary, the description and evidence quote travel in the body, and severity is carried through. Configured once per workspace with your Jira email and API token.
Same shape as Jira, tuned for Linear’s issue model. Artifacts become issues in your configured team, with the description and evidence quote in the body. Configured per workspace with a Linear API key.
Targeted at requirements, decisions, and findings. A pushed artifact becomes a row in the Notion database you configure, with the evidence fields carried along, ready to organise into PRDs, decision logs, or client deliverables.
Artifact notifications to the channel behind your incoming webhook: each message carries the artifact summary and the originating evidence quote, so the channel sees the evidence, not just a link.
For everything else. Point a workspace webhook at your own endpoint: deliveries are JSON, carry the pushed artifacts, and are HMAC-SHA256 signed when you configure a signing secret, so your receiver can verify authenticity. Custom headers are supported for auth schemes we have not met yet.
A documented public API with signed event webhooks, plus more connectors. Deliberately absent from the table above until they ship - the table is a contract, not a wishlist.
Destination credentials are encrypted at rest, scoped to your workspace, and shown only redacted after entry. Pushes run with the credentials you configured, so they can only do what those credentials allow in the destination. When a destination rejects a push, you get a clear per-artifact error, never a silent drop.
Non-negotiable. Every artifact that leaves Citesvue carries its evidence - wherever it lands.
Title, description, and structured fields.
Carried through so downstream triage stays honest.
The exact words that triggered the artifact.
Generic webhook deliveries are HMAC-SHA256 signed when you configure a secret.
Export recordings and their evidence as JSON, CSV, PDF, or Word, or deliver them straight into your own Google Sheets, Docs, and Drive. Account-level deletion is honoured end-to-end. The generic webhook means 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.
