Skip to content

Granola

Meeting notes and transcripts: what was said, decided and promised. Read-only.

Connects with API key
Reads 5 operations
Writes None
Irreversible None
Personal data Attendees, notes and transcripts.
Data stays in AWS Sydney (ap-southeast-2)
  • The folders notes are filed in.
  • Meeting notes the key can see: title, owner, dates, and the full note with its summary, attendees and the calendar event it came from.
  • A note’s transcript, with speaker attribution where Granola identified one.
  • The workspace audit log: who did what and when.

The owner’s private notes are included only when the key belongs to the owner.

Audio, and the private notes of anyone other than the person whose key it is.

Nothing. There are no write operations in this connector.

Connect with an API key. In the Granola app, open Settings, then Connectors, then API keys, and create a key with the note scopes the Stori needs. It starts with grn_.

  • The API key. Nothing else.

These are the names the Integrations page shows beside each tick box, in the order it lists them. Generated from the connector registry; do not edit by hand.

All 5 operations
Operation Kind What it does
list_folders Read List the folders notes are filed in, each with its id, name and parent_folder_id (null at the top level).
list_notes Read List meeting notes the key can see, newest first, as summaries: id, title, owner (name and email), created_at and updated_at in UTC.
get_note Read Retrieve one note in full: the AI summary as summary_markdown and summary_text, the owner’s private notes when the key belongs to the owner, the attendees, t…
get_transcript Read Read a note’s transcript in pages of items, each with the text, start_time and end_time in UTC, and a speaker whose attribution is me (the note-taker) or the…
list_audit_events Read List the workspace audit log, newest first: who did what and when, with the actor (a user, an API key or the system), an action name such as workspace.member…