Connect Granola
Connect Granola with a workspace or personal API key, see which notes Gurusup reads, bring in past meetings, and fix a refused key.
Admins only. From each meeting's notes Gurusup learns what was said, what was decided and who owns the next step. It adds a webhook in Granola to hear about new and edited notes.
At a glance
| Topic | Details |
|---|---|
| Who can connect | Admins |
| What you need | A Granola plan with the API, and a workspace or personal API key |
| What Gurusup reads | Every note the key can access: details, summary, transcript |
| How changes arrive | When Granola finishes or edits a note |
| Past content | Import history, up to the last year |
| Knowledge access | Default access, Restricted or Private, per key. See Who can read it. |
Before you start
- Check your Granola plan includes the API. Gurusup's error says Granola's Business and Enterprise plans do.
- Choose the kind of key. They read different notes:
| Key | Who creates it in Granola | What Gurusup reads with it |
|---|---|---|
| Workspace key | A Granola admin, under Settings → Connectors → Workspace API keys | "Notes shared with your whole Granola workspace, and spaces with API access on. Never private notes." |
| Personal key | Anyone, under Settings → Connectors → API keys | "Your own notes, private ones included, and notes shared with you." |
A personal key brings that person's private notes into Gurusup as an organization source. Restrict it before you connect if they should stay with a few people.
Connect Granola
Open the Granola connector
In the sidebar, open Sources, then Catalog, find Granola (use Search sources if you need to) and click Connect on its row. Its page opens. Next to Organization accounts, click Connect for the organization. The dialog Connect Granola for the organization opens.
Choose who can read it
In the dialog, under Who can read it, keep Default access, or choose Restricted or Private from Access mode and pick the people.
Create the key
In the dialog, under Key type, pick Workspace key or Personal key. The hint under API key says how to create it in Granola.
Paste it and check the folders
Paste the key in API key. Gurusup says "Reading the folders this key reaches in Granola…" and lists Folders this key can access, grouped by space when Granola returns them. Connect stays off until the list loads.
Connect
Click Connect. A message says Granola is connected and the key appears under Organization accounts.
Read the folder preview carefully
The list is a preview, not a filter. Gurusup says: "Gurusup reads every note this key can access, including notes outside any folder. This folder list is a preview. With a workspace key, restricted custom spaces with Granola API access on are included; turn that setting off for any space Gurusup should not read."
If the key reaches more than one space, Gurusup also warns: "Other spaces may be restricted groups. Gurusup will make their notes visible to your whole organization." To keep a space out, turn its Granola API access off before you connect. To keep its notes to a few people, restrict the source.
What Gurusup reads
Each note becomes one document:
| Part | What Gurusup keeps |
|---|---|
| Details | Title, when the meeting was, organiser, note taker, attendees, folders and a link to open it in Granola |
| Summary | Granola's summary |
| My notes | The note taker's own notes, only with a personal key on that person's own notes |
| Transcript | Line by line, with the speaker's name when Granola has it. Otherwise the note taker's name, "Note taker", "Other participant" or Granola's label, such as "Speaker A". |
What Gurusup does not read
- With a workspace key, private notes.
- Notes in a space with Granola API access off.
How changes arrive
| Event | What Gurusup does |
|---|---|
| Granola finishes a note, or someone edits one | Reads it again through the webhook |
| A note comes into the key's reach later, for example it is shared | Reads it, even if it is older than the connection |
| A note is deleted or leaves the key's reach | Nothing. Granola does not tell Gurusup, so what Gurusup learned stays. |
When you connect, only new notes come in. The History section says "Only new content comes in until you import past content." Follow each note on Follow ingestion.
Import past work
Open Import history
On Sources, open the Granola page. Under History, click Import history.
Pick how far back
Pick Last week, Last month, Last 3 months, Last 6 months or Last year. Gurusup counts the notes in that window and shows what the import would use out of what you have left this month, in euros.
Import
Click Import. When it finishes, the row reads, for example, "Imported the last month".
A window you already imported shows "Already imported", and you can always pick a longer one. What happens when the import costs more than you have left, or stops, is in Import history.
Who can read it
Each Granola key is its own source, with its own access.
| Knowledge access | Who reads it in Brain |
|---|---|
| Default access | Everyone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them. |
| Restricted | Only the people you pick. Administrators are not included unless you pick them. |
| Private | Only you. Administrators are not included. |
Gurusup does not copy who can see a note in Granola. With a personal key, the key owner's private notes are read by whoever the access in Gurusup allows. Set Restricted before you connect and it applies before Gurusup reads anything. To change access later, open the Granola page and change Access mode under Knowledge access; it saves as soon as you change it. Restricting later only covers notes that arrive after you save. See Restrict a source to specific people.
Add more keys
You can connect a workspace key and several personal keys side by side, each its own connection and source. Open the Granola page from Sources or Catalog and click Connect for the organization again. Choose the access under Who can read it, paste the key, wait for the folders and click Connect. Organization accounts lists every key with its status and when it last synced; click a key's name to open its own settings, and use the three dots on its row to Rename or Disconnect it.
Check that it worked
Check the badge
On Sources, open the Granola page. Under Organization accounts, the badge reads Connected. The folders Gurusup reads are listed in the dialog before you connect, not on this page.
Take a note
Take a short meeting in Granola and let it finish the note.
Follow it
Open Ingest and pick the Granola source in the filter. The note moves to Learned.
Reconnect
If Granola stops accepting a key, for example it was revoked or API access was turned off, the connection shows Needs reconnect. Click Reconnect on the key's row under Organization accounts. The dialog says "Granola needs to be reconnected with a new key."
Create a new key, paste it in the dialog and click Reconnect. With several keys, click Reconnect on the affected one. Gurusup keeps that connection's access and imported history. You can replace a working key the same way.
Disconnect
On Sources, open the Granola page. Under Danger zone, open the menu on Disconnect, choose Disconnect and confirm. With several keys, it removes only the connection you opened. Gurusup removes the webhook it added in Granola (other webhooks stay), and what it learned stays; the key stays valid in Granola until you delete it there. See Remove, disconnect and what stays.
If it does not work
These show under the key while Gurusup reads it, or after "Could not connect Granola." when you click Connect:
| Message | What to do |
|---|---|
| "Granola didn't accept this API key. Copy it again from Settings → Connectors in Granola (API keys or Workspace API keys) and paste it here." | Copy the key again, or create a new one. |
| "Granola's API access settings don't let this key read notes. Ask a Granola admin to allow API access for members, or to create a workspace API key in Settings → Connectors → Workspace API keys." | Ask a Granola admin to allow API access, or use a workspace key. |
| "Your Granola plan doesn't include the API. Granola's Business and Enterprise plans do; once you're on one, you can create an API key in Settings → Connectors." | Change your Granola plan, then create a key. |
| "Granola didn't accept this key for reading notes. Create a new one in Granola under Settings → Connectors → API keys, or Workspace API keys if you're a Granola admin." | Create a new key. |
| "This Granola connection was removed. Add a new connection with your API key." | Click Connect for the organization again. |
| "We couldn't read your Granola workspace because of a problem on our side. Nothing was connected. Try again in a few minutes, and contact support if it keeps failing." | Try again later. Contact support if it keeps happening. |
| "We couldn't connect Granola because of a problem on our side. Nothing was connected. Try again in a few minutes, and contact support if it keeps failing." | Same. |
| "We couldn't read your Granola folders because of a problem on our side. Your connection is unchanged. We've logged the problem. Contact support for help." | The connection still works. Contact support if it keeps happening. |
| "The import didn't finish. Try again, and contact support if it keeps failing." | Click Try again. If it keeps failing, contact support. |
| Notes stop arriving | What to do |
|---|---|
| The badge reads Needs reconnect | See Reconnect. |
| The key does not reach the note | A workspace key never reads private notes, and a space with API access off is not read. |
| The note is older than the connection | Use Import history. |
| Ingestion paused, Demo Mode, or the item Paused on Ingest | See Connector troubleshooting. |
Still stuck? Contact support with the note's title and when it was taken.