Granola
Granola is an AI notetaker that records and summarizes meetings. Connecting it brings those notes and transcripts into Sonora, where they feed sentiment analysis, eCSAT, feature-request detection, and the customer-meeting view in profiles and chat — the same signals Sonora draws from Gong and Chorus calls.
If you run Granola alongside a calendar or another conversation source, Sonora deduplicates the same physical meeting across sources so one conversation doesn’t appear twice. A Granola note for a call that’s also on Google Calendar merges into a single meeting with provenance from both.
What syncs
Section titled “What syncs”- Meeting notes (title, summary, owner, timing)
- Transcripts with speaker attribution
- Attendees and their email domains (used for customer matching)
The integration is read-only. Notes stay in Granola; Sonora pulls a copy of the content the API key can reach.
What the key controls
Section titled “What the key controls”Sonora only sees the notes your Granola API key can access — there’s no way to broaden that from Sonora’s side. The key type determines coverage:
| Key type | Where to issue it | What syncs |
|---|---|---|
| Enterprise (recommended) | Granola workspace admin | Notes shared to your workspace’s Team space. Private notes do not sync. |
| Personal | Any Granola user | Notes the key holder owns or has been shared on. |
Use an enterprise key for workspace-wide coverage — it’s the only way to capture meetings across your whole team rather than a single person’s notes. A personal key works for a narrow pilot but misses anything that user wasn’t on.
If notes are missing after a sync, move them into Team space (or share them with the key holder) inside Granola and re-run the import.
Prerequisites
Section titled “Prerequisites”- A Granola workspace
- For workspace-wide sync: admin access to issue an enterprise key
- The Granola desktop app (where keys are generated)
1. Generate a Granola API key
Section titled “1. Generate a Granola API key”- Open the Granola desktop app.
- Go to Settings → API.
- Create a key labeled “Sonora Integration” and copy it.
For full coverage, generate this as an enterprise key from a workspace admin account. See What the key controls.
2. Connect in Sonora
Section titled “2. Connect in Sonora”- Settings → Integrations → Granola → Connect.
- Fill in:
- API key — the key you just generated
- First sync lookback (days) — how far back to pull on the initial import (default: 90)
- Click Test connection to confirm the key, then save.
After the first backfill, Sonora pulls new and updated notes incrementally on the schedule set in the Granola card.
Customer matching
Section titled “Customer matching”Notes match to Sonora customers by attendee email domain. A note whose participants don’t match a known customer is skipped rather than stored as unattached — add the customer or its domain in Sonora and re-run the import to pick it up.
Disconnect
Section titled “Disconnect”From Settings → Integrations, disconnect the Granola card. To revoke access on Granola’s side, delete the API key in Settings → API in the desktop app.
Troubleshooting
Section titled “Troubleshooting”“Connection failed” on test — Confirm the key was copied in full and hasn’t been rotated in Granola. Enterprise and personal keys both authenticate; the difference is in what they can read, not whether the connection succeeds.
Notes missing after sync — Almost always a scope issue. An enterprise key only sees Team space notes; a personal key only sees the holder’s notes. Move the meetings into Team space or share them with the key holder, then re-run the import.
A meeting shows no transcript — Granola processes recordings asynchronously, so a transcript can lag the meeting. Sonora retries automatically and picks it up on the next incremental sync.