MemorySync
Integrations

Granola integration

Retrieve AI meeting notes, summaries, and transcripts from the Granola folders an administrator approves. Recover what a meeting decided — and what was actually said — with attendees, meeting time, and a link back to the note in Granola.

What meeting knowledge becomes retrievable

Recover what a meeting decided — and what was actually said — with attendees, meeting time, and a link back to the note in Granola.

AI summaries

The generated summary for each meeting, with attendees and timing.

Full transcripts

Speaker-attributed transcripts, indexed separately from the summary.

Participant-scoped notes

Private folder content limited to each meeting’s participants.

Connecting with an API key

Granola has no sign-in redirect. An administrator creates a key in the Granola desktop app under Settings, then Connectors, then API keys, and pastes it into MemorySync. The key is verified against Granola before the connection is saved, so a mistyped key fails immediately rather than as a silent sync failure later.

Prefer a workspace key
A workspace key belongs to the workspace rather than a person: it does not expire and keeps working after the administrator who created it leaves. Both kinds require a Business or Enterprise plan.
  • A Granola workspace on a Business or Enterprise plan, which is what allows API keys to be created.
  • A Granola API key, ideally a workspace key so it does not expire or depend on one person’s account.
  • A MemorySync project for the imported meeting knowledge.

Choose folder scope

Granola workspace
Approved folders
Summaries and transcripts
Outside this path: notes that are in no approved folder, and notes with no generated summary
Folder boundary
Only folders an administrator approves are read, and a note that is in no approved folder is never indexed. Private folder content is retrievable only by that meeting’s participants. Granola notes that have no generated summary yet are not available through its API at all.

Summaries and transcripts are separate

Each meeting produces two retrievable items: the AI summary, and the full transcript. They are indexed separately so a summary edit does not force the whole transcript to be reprocessed, and so transcripts can be declined without losing summaries.

ItemContainsBest for
SummaryTitle, attendees, meeting time, and the generated summaryWhat was decided
TranscriptSpeaker-attributed lines for the whole meetingWhat was actually said

Guided first connection checklist

Local planning guide
Plan your Granola import

Check items for your own planning. Nothing here changes a live connection.

0 of 4 planning steps complete

Initial and incremental ingestion

  1. 1
    Add the API key

    An administrator pastes a Granola API key, which is verified before it is saved.

  2. 2
    Approve folders

    They select each folder to index; approving a folder covers its subfolders.

  3. 3
    Import history

    MemorySync reads approved folders within the configured history window.

  4. 4
    Track new meetings

    New summaries, edits, and newly shared notes arrive as they happen.

Verify with a real meeting question

Ask about a decision from a meeting in an approved folder. Confirm the result names the right meeting and links back to the note in Granola before widening folder access.

Troubleshooting and related sources

Why was the API key rejected?

Creating API keys requires a Granola Business or Enterprise plan. On Enterprise, an administrator may also need to enable API access scopes for members before a usable key can be created.

Why are no notes appearing?

Check that at least one folder is approved. Notes kept outside any folder are deliberately skipped, because being able to read a note does not establish that it is shareable.

Why is a recent meeting missing?

Granola only exposes notes that already have a generated summary. A meeting still being processed will appear on a later sync.

Why can a colleague not retrieve a private meeting?

Private folder content is limited to that meeting’s participants, and each participant must be linked to a MemorySync account.