Citesvue
Product · Integrations

Your workflows already exist. We route evidence into them.

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. Evidence comes in from six meeting platforms or any uploaded recording, and goes out to Jira, Linear, Notion, Slack, or your own webhook - with the evidence attached.

Connect your first toolAsk about the roadmap
Push payload contract5 native + webhooks + REST
Artifact
BUG · high
14:23.4
"Export button is broken."
router
  • Jira
  • Linear
  • Notion
  • Slack
  • Webhook
quote · verbatim
speaker
timestamp · deep link
frame · embedded
severity → priority
audit id
Where evidence comes in

Seven ways in. All of them first-class.

The assistant joins six meeting platforms with a visible notice - or skip the bot and upload a recording from any tool. Every path produces transcript-first content; optional visual evidence is added only when requested.

The integration map

What connects, what travels, where it lands.

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.

DestinationWhat you can pushHow it landsDestination pickerConnect
Jira logoJiraFindings (bugs, action items, requirements…)Typed issue (bug → Bug) · severity → priority · evidence quoteLive project pickerOAuth, or Jira email + API token
Linear logoLinearFindingsIssue with severity → priority · evidence quoteLive team pickerOAuth, or Linear API key
Notion logoNotionFindings (single or batch) · recaps · transcripts · reports · Q&A answers · visual timelines when readyStructured page blocks with evidence fieldsLive page / database pickerOAuth, or internal integration secret
Slack logoSlackFindings (single or batch) · recaps · Q&A answersRich message blocks · severity markers · evidence quoteLive channel pickerOAuth, or incoming webhook URL
WebhookEverything aboveVersioned JSON envelope · HMAC-SHA256 signed when a secret is setYour endpoint URLURL + optional signing secret + custom headers

Findings push one at a time to Jira and Linear by design - each becomes a first-class issue, not a bulk dump. Notion, Slack, and the webhook also accept batches.

Where push lives

Four places in the product, one delivery pipeline.

A single finding

From the review queue or the finding itself, once it is approved. The destination list shows only tools that accept findings, with your unconnected tools visible but disabled - one click into Settings to connect them.

A batch of findings

Send a session’s approved findings together to Notion, Slack, or your webhook - a findings register in one push.

The recording itself

The Push menu on any recording sends its full report, recap, transcript, or, when visual evidence is ready, timeline to the destinations that accept that content shape. It never sends an empty visual section.

A grounded Q&A answer

When the copilot answers with citations, push the answer - citations included - to Notion, Slack, or your webhook. The claim and its proof travel together.

Delivery you can trust

Queued, retried, deduplicated, visible.

A push that silently vanishes is worse than no integration at all. Delivery is engineered like the rest of the evidence layer: honest about its state at every step.

  • Queued, then delivered

    Every push is written down before it is sent. The app says "Queued" because that is the truth - and seconds later the delivery record says "Delivered".

  • Retried automatically

    Transient provider failures retry with exponential backoff. Permanent ones (a revoked credential, a deleted project) fail fast with the provider’s actual error.

  • Never duplicated

    Pushing the same finding twice links the existing issue instead of filing a second one - and on Jira, Linear, and Notion it updates the existing item in place.

  • Visible and retryable

    A delivery activity panel in Settings shows every push, its status, and a one-click retry.

Auth & permissions

Push respects both ends of the permission check.

Credentials - OAuth grants and pasted tokens alike - are encrypted at rest, scoped to your workspace, and shown only redacted after entry. Pushes run with the credential you connected, so they can only do what that credential allows in the destination. On the Citesvue side, viewers cannot push at all, and findings must be approved in review before they can leave the workspace. When a destination rejects a push, you get the provider's actual error on the delivery record, never a silent drop.

The generic webhook

For every tool we have not met yet.

Point a workspace webhook at your own HTTPS endpoint and receive everything the native connectors can.

  • Versioned JSON envelope carrying the pushed content, the source recording, and an idempotency key.
  • HMAC-SHA256 signature over timestamp + body when you configure a signing secret, so your receiver can verify authenticity and reject replays.
  • Custom headers supported for auth schemes we have not met yet; reserved headers are protected.
  • Connecting sends nothing - no unsolicited test event ever lands on your endpoint.
Portability

No vendor lock-in. We mean it.

Export recordings and their evidence as JSON, CSV, PDF, or Word. Where Google Workspace export is enabled for the connected workspace, selected content can be delivered into your own Sheets, Docs, and Drive. Account-level deletion is honoured end-to-end, and the generic webhook means the evidence layer is portable - nothing is trapped in the UI.

Availability

On Pro and above. Honest about what is next.

Connecting an integration is available on every plan; pushing requires Pro, Team, Business, or Enterprise. On the roadmap: automation rules (auto-push on conditions you set), a documented public API with signed event webhooks, and more connectors. Deliberately absent from the table above until they ship - the table is a contract, not a wishlist.

Common questions

What technical buyers ask about integrations.

  • Pick a destination in Settings and sign in with the provider - a standard OAuth consent, after which Citesvue shows you the real projects, teams, pages, or channels your account can reach. If your team prefers service credentials, every non-Google destination also accepts a pasted API token or webhook URL.
  • OAuth tokens and pasted credentials are encrypted at rest with an additional application-level layer, scoped to your workspace, and shown only redacted after entry. They are used for exactly two things: listing destinations you can pick, and delivering pushes you trigger.
  • Members and above. Viewers can read everything in the workspace but cannot send content out of it. Connecting an integration is available on every plan; pushing requires Pro or above.
  • The downstream item remains in your tool. Deleting the recording removes the source evidence from Citesvue.
  • Not yet. Every push is triggered by a person, reviewed first in the case of findings. Automation rules (for example, auto-filing critical bugs) are on the roadmap.
  • Not yet. A documented API with signed event webhooks is on the roadmap, and the pricing page will only show it when it ships. The signed generic webhook covers outbound delivery today.
  • Not today. Jira, Linear, Notion, and Slack are the shipped connectors; the generic webhook covers custom destinations in the meantime.
Continue exploring

What feeds the integrations, and where push policies live.

Closing argument

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.

Start free - no credit cardBook a 20-minute walkthrough
  • 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.