Granola: what this connector can do

Member·4 minutes to read

What this page is for

docs/connectors/granola.md is the setup guide — creating a Granola API key and choosing its two access scopes; there is no vendor application to set up. This page is the other half: what Granola actually lets a bot do once it is connected to your account, what it asks you for along the way, its limits, and how to take the connection away again, in Botseon and at Granola.

Read your meeting notes, their AI summaries and transcripts, with a key from your Granola workspace.

What a bot can do with it

Read — Granola tells a bot things, nothing changes

Tool	What it does
`granola.list_folders`	List the folders this key can access.
`granola.list_notes`	List meeting notes, newest first, optionally in one folder or a created-at window.
`granola.get_note`	Read one meeting note by id: its title, attendees, calendar event and AI summary.
`granola.get_transcript`	Read the transcript of one meeting note, one page at a time.

A note a bot reads comes with a link back to it in Granola, its summary, who attended, and the calendar event's organiser and invitees. A bot can also ask for only the notes that changed since a given time, and transcript lines say whether you (the note's owner) or someone else spoke, with the speaker's name or an anonymous label such as "Speaker A" when Granola has one. Where Granola does not know who spoke (for example on its iPhone app), the line says so rather than guessing.

A note shows up only once Granola has finished its AI summary, so a meeting that just ended may take a few minutes to appear. A bot sees exactly the notes your key can see: your own notes and notes shared with you need the Personal notes scope, team notes need Public notes and a folder everyone in the workspace can see.

Write

This connector has no write tools yet. A bot can only read through it.

The permissions it asks for, in plain words

Every call a bot makes through this connector is tagged with what kind of thing it is. Only the tags below ever apply here — a tag this connector's tools never carry is not listed, because it can never ask you for it.

read — Looks something up. Nothing changes, and nothing is sent anywhere. A bot never has to ask first for this.

Limits

Read your meeting notes, their AI summaries and transcripts, with a key from your Granola workspace. Nothing outside that list is possible through this connector, however a bot is asked to use it.

Granola is also only ever as wide as the scopes ticked on the key you paste — the checklist and what each scope means are on the setup page, docs/connectors/granola.md.

Disconnecting

In Botseon

Open Plugins from the sidebar, press this connector's card to open its detail page, and under Accounts press Remove next to the account — or Uninstall to remove the plugin and every account connected to it at once. Either one revokes the stored connection immediately: nothing more is read or changed through it from that moment on. Install a plugin walks through the same screen step by step.

At Granola

Removing the account in Botseon deletes the stored key from Botseon, but the key itself stays valid at Granola until you delete or rotate it yourself. Do that from the Granola desktop app, under Settings → Connectors → API keys — the same place you created it — which is the only way to be sure nothing else can use it, since Botseon has no way to revoke a key it did not issue.

What Botseon keeps, and how your data is used

Whatever a bot reads or writes through this connector becomes part of your conversations and the record of that run — the same records, and the same retention schedule, as everything else a bot works on. Botseon is the processor for that content; your organisation decides what it may read and remember, and can delete it sooner than the schedule would on its own.

Your data is sent to a model provider only to produce the bot's answer, and for nothing else — it is not used to train any model. The Privacy Policy's Models and How long we keep it sections have the full detail, including exactly how long each kind of record is kept for.