Workflows

This page is the practical version of the docs.

Instead of learning Gran feature by feature, start from the outcome you want.

I Want A Local Workspace For My Granola Archive

gran init

Use this path when you want a better local Granola workspace with a sync loop, fast search, and durable exports.

What you end up with:

• a local meeting archive on disk
• a browser workspace with latest meetings, folders, and search
• background sync you can inspect later instead of guessing what happened

I Want Everything In Obsidian

gran init
gran kb add --name "Work vault" --kind obsidian-vault --output ~/Vaults/Work --daily-notes-dir Daily
gran export --kb work-vault

Use this when Obsidian is your system of record.

Obsidian vault publishing supports:

• meeting notes and transcripts in stable subdirectories
• markdown transcripts
• note/transcript backlinks
• optional daily-note placement

If you want API-backed destinations like Notion, Capacities, or Tana, keep Gran as the source app and hand those publish flows off to another tool instead of expecting Gran to own every remote API.

I Want Raw Exports I Control

gran init
gran export
gran export --folder Team
gran exports list

Use this when you want durable local files without touching any advanced automation.

gran export is the normal path because it writes notes and transcripts together unless you ask for only one of them.

I Want To Build On Top Of Gran In My Own Code

npm install @kkarimi/gran-sdk

Use the SDK when you want the same local-first runtime, knowledge bases, and export logic inside Node or TypeScript code instead of shell commands.

See SDK for examples.

I Want Gran To Trigger Another Local Tool

gran events --format jsonl --follow

Use this when Gran should act as the local source app and something else should do the downstream work.

This is the simplest universal seam:

• follow meeting and transcript change events as JSON lines
• fetch the affected item with gran meeting get ... --format json
• keep your automation outside Gran instead of tightly coupling the runtimes

I Want To Stay In The Terminal

gran init

Choose the terminal workspace in guided setup when you want the shared local runtime and a keyboard-first workspace without dropping to docs first.

I Want Reviewable AI Notes Before Anything Gets Published

gran init --provider openrouter

Then:

1. finish guided setup and land in the browser workspace
2. open Settings -> Advanced
3. enable the automation plugin
4. keep or edit the starter harness
5. review drafts in the Review workspace before publishing them

Use this path when you want Gran to help produce notes, but you still want human approval before they are written into a vault or downstream system. This is an advanced Gran workflow, not the default Gran story.

Which Page Next?

• Open Getting started if you have not run gran init yet.
• Open Exporting if you want to publish into folders or Obsidian vaults.
• Open Integrations if you want scripts, event followers, or external tools on top of Gran.
• Open SDK if you want to embed Gran in local scripts or apps.
• Open Automation if you want Gran's advanced local review-first note flows.