obsidian-granola

Granola meeting notes

Import meeting data into linked meeting and transcript notes. Read the vault's instructions before note work and use its available CLI or connector; tool names vary by environment.

Choose the workflow

• Import: requests to sync or fetch a meeting follow the steps below. Finish after the notes are saved, linked, and read back; auditing and enrichment are separate unless requested.
• Process: requests to process a meeting, audit and enrich it, or resume after pasting a transcript follow Process a meeting. Reuse existing notes before importing anything.
• Recording: when the input is an audio/video file, use transcribe-audio only if local transcription is requested and the runtime supports it. Feed the resulting transcript into processing; the other branches need no local transcription runtime.

An ambiguous meeting needs identifying before any writes. Carry supplied titles, destinations, and earlier approvals forward.

1. Capture Intent & Context

First, determine which meeting the user wants to sync.

• If they say "my last meeting", you will need to list recent meetings to find it.
• If they specify a person or topic, search or list recent meetings to identify the correct one.
• If the user says they already have an existing prepared note for this meeting in Obsidian, append the Granola contents to their existing note, and create a separate transcript note.
• Otherwise, you will generate a new title and create both the meeting note and transcript note from scratch.

2. Fetch Granola Data

Use the connected Granola tools to list or search meetings, read the selected meeting's summary/action items/private notes, and fetch its verbatim transcript. Discover the tools actually exposed rather than requiring one provider's identifiers.

If transcript access fails or is unavailable, continue importing the meeting and save an empty transcript staging note for manual paste. Check the returned data and saved note; plan restrictions are a possible reason, not a fact to assume.