Granola exposes it through the API only after both parts are ready.
Before you start
- A Granola Business or Enterprise plan for API access.
- A Personal or Workspace API key; Workspace keys are recommended for team syncs.
1. Open Granola connector settings
In the Granola desktop app, open Settings → Connectors.
2. Choose the API key scope
Create a Personal or Workspace API key. For a Personal key, choose the note access Permute may sync.
Granola offers Personal keys and Workspace keys on Business and Enterprise plans. A Personal key follows one user’s note access. A Workspace key is managed for the workspace and is the better fit for a team connection.
For a Personal key, choose its note scope before copying it. Personal notes and Public notes are different access choices. A Workspace key cannot read private notes that have not been shared with the workspace.
3. Copy the key
Copy the key.
Granola makes a note available through its API after both a summary and transcript exist. Notes still being processed, and manual notes without that material, do not appear through the API. Check the note in Granola before troubleshooting a missing Permute row.
Personal keys follow their selected note scope. Workspace keys can read public notes and notes in spaces with API access enabled; they cannot read unshared private notes.
4. Add Granola in Permute
In your workspace, open Connectors, select Add Connector, choose Granola, and name the account.
Under Sync which data?, choose an option:
| Choice | What it does |
|---|---|
| Everything | Selects all discovered data available to this connection. |
| Select manually | Choose the tables Permute syncs. |
- Paste the key into API Key and select Connect.
5. Choose tables (manual selection)
If you chose Select manually, open the connector after connecting. Use the checkboxes to select at least one table, then select Save selection.
6. Check the first result
- Choose a Granola note with both summary and transcript complete.
- Check that the key’s Personal or Workspace scope includes that note.
Available data
| Data group | What the setup screen covers |
|---|---|
| Meeting content | Notes, summaries, and transcripts. |
| Organization | Folders within the key’s permitted note scope. |
Choose a key for the note scope
Granola Personal keys and Workspace keys have different reach. A Personal key can use its selected personal or public note scope. A Workspace key can reach public notes and notes in spaces where API access is enabled; it does not reach unshared private notes.
Use a Personal key when the intended notes belong to one person’s allowed scope. Use a Workspace key for a team collection whose sharing and space settings allow API access. Check the scope in Granola before treating a private note as a failed sync.
Wait for a complete note
Granola exposes a note through its API only after it has both an AI summary and a transcript. A manual note or a meeting still being processed can appear in the app before it qualifies for the API.
For a first check, choose a meeting note with both parts complete. Confirm that the key’s scope includes it, then compare the note title and content. If a newer note is absent, inspect its processing state in Granola before changing the key.
Review space and key changes
Workspace keys do not have a fixed expiry in Granola. Access still depends on which spaces allow the API and how notes are shared. A space setting or note-sharing change may alter what the same key can read.
Granola lets an authorized user revoke a key. If a previously working connection loses its notes, check whether the key still exists and whether the notes remain inside its scope. Use one known public or enabled-space note to separate a key failure from a sharing change.
Troubleshooting
| Problem | What to check |
|---|---|
| A private note is absent | Check whether the Personal or Workspace key can read it. |
| A new note is absent | Check that Granola finished its summary and transcript. |