Guide · Integrations · Notion

Meeting records that file themselves, citations intact.

Notion is the most capable destination: recaps, transcripts, timelines, single findings, whole finding sets, and cited answers all arrive as structured pages under a parent you choose. The one rule: share the destination with Citesvue first.

Updated26 August 2026Read5 minNeedsWorkspace admin; paid plan to push
Setup

Five steps, one Notion-specific rule.

The rule: connecting the workspace grants nothing by itself - access is per page, and you choose which.

  1. STEP 01

    Open the integrations settings

    Settings, then Integrations under Push destinations. Connecting needs a workspace admin or owner.

  2. STEP 02

    Connect Notion

    On the Notion card, choose Connect and sign in. Notion asks you to pick which pages Citesvue may access - that selection on the consent screen is the whole permission model, so include the page you want content delivered under.

  3. STEP 03

    Pick the destination page

    The picker lists the pages you shared, most recently edited first. Everything Citesvue sends is created as a new page under the one you pick, so choose a parent like "Meeting records" rather than a page you write in daily.

  4. STEP 04

    Confirm the card reads connected

    The card shows the destination page by name. If the picker comes back empty, nothing has been shared with Citesvue yet - share a page from the Notion side and read the list again.

  5. STEP 05

    Send something

    From any recording: push the recap, the transcript, a single finding, or a whole set of findings. The app confirms "Queued", and the new page appears under your destination with the evidence formatted, not pasted.

What you can send

Five kinds of content, all formatted for Notion.

Long content paginates cleanly instead of truncating; anything elided says so on the page.

A single finding

A page titled after the finding: type and severity callout, description, the evidence quote, and a link to the moment in Citesvue.

A set of findings

One organised page, not a page per finding: a findings table when the set is large enough, then sections per type with severity-ordered entries.

Recap

The meeting recap as a page: overview, decisions, action items with owners, topics.

Transcript and timeline

The full transcript, or the moment-by-moment timeline, as readable pages under the same parent.

A cited Q&A answer

The question, the answer, and each citation with its quote and timestamped link.

When it goes wrong

Four states and their fixes.

  • The picker is empty

    Nothing is shared with Citesvue yet. In Notion, open the destination page and share it with the Citesvue connection (or re-run Connect and tick the page on the consent screen), then read the list again.

  • Deliveries fail after moving or deleting the page

    If the destination page is deleted or un-shared, deliveries fail with the reason in Integration activity. Pick a new destination page from the card.

  • "Reconnect needed" on the card

    Notion stopped accepting the credential. Reconnect from the card; your destination choice is kept.

  • A re-push looks different from an edit history

    Re-pushing the same content updates the existing page by rewriting its body - the page keeps its location and link, but manual edits made inside it are replaced. Treat delivered pages as generated output, and write commentary on a sibling page.

Delivery states and retries work the same for every destination - see troubleshooting.

Common questions

Notion integration, answered.

  • A paid Citesvue plan to push (connecting works on every plan), the workspace admin role in Citesvue, and a Notion account that can share the destination page with a connection.
  • Yes. Create an internal integration in Notion, copy its secret into the connect dialog along with the database ID from the destination URL, and share that database with the integration from its menu under Connections. The sign-in path with a page destination is the recommended one.
  • No. Notion access is per page: Citesvue can only reach what you explicitly shared on the consent screen or from a page menu. Sharing the destination parent is enough.
  • Pages accept any content shape, so recaps, transcripts, and finding sets all arrive fully formatted. Database destinations from earlier connections keep working, with each delivery as a row.
  • They stay in Notion - they are your pages. Citesvue forgets the credential and stops sending; reconnecting later resumes deliveries under whatever page you pick.
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.

  • 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.