Granola + MemorySync

Overview

MemorySync's native Granola provider reads only the folders a workspace administrator explicitly approves. It backfills meeting history, indexes each note’s AI summary and its speaker-attributed transcript as separate retrievable items, and keeps up with new meetings through Granola’s webhooks. Because Granola emits no deletion event, a scheduled reconciliation pass detects notes removed at the source and purges the memories derived from them.

Setup status and requirements

Supported version

Repository implementation reviewed 2026-08-06

Last setup review

2026-08-06

Permissions

A Granola API key created in the desktop app under Settings, then Connectors, then API keys. Creating API keys requires a Granola Business or Enterprise plan, and webhooks are gated on the same plans. Workspace keys are preferred over personal keys because they do not expire and are not tied to an individual account. On Enterprise plans, a workspace administrator may need to enable API access scopes for members first.

Limits

Only folders an administrator approves are read, and a note that is in no approved folder is never indexed, because Granola’s API offers no way to determine which scopes a key carries. Workspace-visible folder memories are readable across the organization. Private folder memories are readable only by that meeting’s participants, resolved at query time from the note’s attendees, and require those participants to be linked to MemorySync accounts; private folders are disabled unless the deployment enables them. Granola only exposes notes that already have a generated AI summary, so a meeting still being processed appears on a later sync. Initial backfill is bounded by a configurable history window (90 days by default) and a per-run note ceiling, because Granola returns no note content in list responses and permits roughly five requests per second. Webhooks require an HTTPS public host; without one the connector falls back to scheduled synchronisation.

Capabilities

• Per-folder administrator approval
• API key connection with server-side verification
• Summaries and transcripts indexed separately
• Speaker attribution preserved in transcripts
• Private folders scoped to each meeting’s participants
• Webhook updates for new, regenerated, and edited notes
• Per-folder incremental watermarks
• Scheduled reconciliation for deleted notes
• Credential redaction before indexing
• Folder exclusion policy covering HR, legal, and review names
• Signed webhook verification

Use Cases

Explore More