Connect Granola to Rig

Before you start

• API keys need a Business or Enterprise plan. Any member of the workspace on one of those plans can mint a key, so this is not necessarily an admin task.
• On Enterprise, an admin controls which scopes are offered to you in the first place. If a scope you expected is not on the screen, that is why.

Create the API key

1. In Granola, click your account at the bottom left, then Settings.
2. Go to Connectors, then Workspace API keys.
3. Click Create new key.
4. Choose the note access scopes. Personal notes and public notes are separate choices, and the key sees exactly what you tick.
5. Copy the key. It starts with grn_.

Connect it in Rig

1. In Rig, open Connections and go to Sources & actions.
2. Search for Granola and open the card.
3. API key: paste the grn_ key.
4. Folder IDs: optional. Leave it blank to sync every note the key can see. To narrow the sync, paste one or more folder IDs separated by commas. They look like fol_ followed by an identifier, and each one covers that folder and everything nested under it.
5. Earliest note date: optional. Notes updated before this are not fetched. It defaults to the start of 2024, which is early enough that most workspaces can ignore it.
6. Click Test, then Sync.

What Rig pulls in

Granola lands in its own granola schema, in three tables.

• Notes: one row per meeting, with the metadata and the timestamps. This is the index.
• Note details: the full note body and the transcript, fetched per note and joined back to it. This is the table with the words in it.
• Folders: the workspace folder hierarchy, which is what makes folder IDs findable and lets you group meetings by however your team has organised them.

Notes sync incrementally on their updated timestamp, so a note edited after the meeting is re-read rather than left stale. Folders are refreshed in full each run, which is cheap at the size a folder tree tends to be.

Good to know

• Folder scoping is a real reduction in what leaves Granola, not a filter applied afterwards. With folder IDs set, Rig requests only those folders, so notes outside them are never fetched. That makes it a reasonable way to keep, say, one-to-ones out of the warehouse entirely.
• The transcripts are the point, and they are large. Note details carries the full text of every meeting, so this connector produces more text than most and is worth thinking about before you sync a workspace-wide history.
• The earliest note date only applies to a connection that has not synced yet. Once a sync has run, its stored position takes over and the date stops being consulted, so changing it later has no effect until a full resync clears that position.
• One key, one view of the workspace. Two people minting keys with different scopes get different amounts of data, so it is worth recording which account a production key belongs to.

Troubleshooting

• There is no API keys section: the workspace is not on Business or Enterprise. The plan gates the feature, not your role.
• Old meetings never appear: they predate the earliest note date. Lowering it and running an ordinary sync will not bring them in, because the stored sync position takes precedence once a connection has run. Lower the date and run a full resync, which clears that position and re-reads from the new floor.

What people use this for

• Turn meeting notes into searchable structured data
• Scope which meetings reach the warehouse
• Surface customer and deal context from calls

More ideas for using Granola