granola-toolkit

General toolkit to do more with Granola notes and transcripts.

Install

From npm:

npm install -g granola-toolkit
granola --help

Without a global install:

npx granola-toolkit --help

For local development:

curl -fsSL https://vite.plus | bash
vp help
vp install

Run

Installed CLI:

granola --help
granola notes --help
granola transcripts --help

Local build:

vp pack
node dist/cli.js --help
node dist/cli.js notes --help
node dist/cli.js transcripts --help

You can also use the package scripts:

npm run build
npm run notes -- --help
npm run transcripts -- --help

Examples

Export notes:

node dist/cli.js notes --supabase "$HOME/Library/Application Support/Granola/supabase.json"

Export transcripts:

node dist/cli.js transcripts --cache "$HOME/Library/Application Support/Granola/cache-v3.json"

How It Works

Notes

notes exports Granola's generated meeting notes, not the raw transcript.

The flow is:

1. read your local supabase.json
2. extract the WorkOS access token from it
3. call Granola's paginated documents API
4. choose the best available note content for each document
5. convert ProseMirror content into Markdown
6. write one Markdown file per document into the output directory

Content is chosen in this order:

1. notes
2. last_viewed_panel.content
3. last_viewed_panel.original_content
4. raw content

Each note file includes:

• YAML frontmatter with the document id, created timestamp, updated timestamp, and tags
• a top-level heading from the note title
• converted note body content

Transcripts

transcripts exports Granola's locally cached transcript segments.

The flow is:

1. read Granola's cache JSON from disk
2. parse the cache payload, whether it is double-encoded or already an object
3. match transcript segments to documents by document id
4. format segments as [HH:MM:SS] Speaker: Text
5. write one .txt file per document into the output directory

Speaker labels are currently normalised to:

• You for microphone
• System for everything else

Incremental Writes

Both commands are incremental. They only rewrite an export file when the source document appears newer than the file already on disk.

That means repeated runs are cheap, and you can safely point the CLI at the same output directory over time.

Config

The CLI reads configuration in this order:

1. command-line flags
2. environment variables
3. .granola.toml
4. platform defaults

Supported config keys:

debug = true
supabase = "/Users/yourname/Library/Application Support/Granola/supabase.json"
output = "./notes"
timeout = "2m"
cache-file = "/Users/yourname/Library/Application Support/Granola/cache-v3.json"
transcript-output = "./transcripts"

Supported environment variables:

• DEBUG_MODE
• SUPABASE_FILE
• OUTPUT
• TIMEOUT
• CACHE_FILE
• TRANSCRIPT_OUTPUT

Development Checks

Before pushing changes, run:

vp check
vp test
vp pack
npm pack --dry-run

What those do:

• vp check: formatting, linting, and type checks
• vp test: unit tests
• vp pack: builds the CLI bundle into dist/cli.js
• npm pack --dry-run: shows the exact npm package contents without publishing

vp build is for web apps. This repo is a CLI package, so the build step here is vp pack.