Granola Meeting Notes

Granola Meeting Notes

Access your Granola meeting notes, transcripts, and summaries directly from Claude Code. This skill reads Granola's local cache file - no API keys or authentication required.

Prerequisites

• Granola desktop app installed on macOS
• At least one meeting recorded in Granola

Available Commands

List Recent Meetings

${CLAUDE_PLUGIN_ROOT}/bin/granola.js list [--days N] [--all]

Lists meetings from the last N days (default: 7). Use --all to show all meetings.

Examples:

# List last 7 days
${CLAUDE_PLUGIN_ROOT}/bin/granola.js list

# List last 30 days
${CLAUDE_PLUGIN_ROOT}/bin/granola.js list --days 30

# List all meetings
${CLAUDE_PLUGIN_ROOT}/bin/granola.js list --all

Show Meeting Details

${CLAUDE_PLUGIN_ROOT}/bin/granola.js show <meeting-id> [--transcript]

Shows full details for a specific meeting. Use partial IDs (first 8 characters work).

Examples:

# Show meeting notes
${CLAUDE_PLUGIN_ROOT}/bin/granola.js show 02b2432a

# Include full transcript
${CLAUDE_PLUGIN_ROOT}/bin/granola.js show 02b2432a --transcript

Search Meetings

${CLAUDE_PLUGIN_ROOT}/bin/granola.js search <query>

Search meetings by title, notes content, summary, overview, or participant names/emails.

Examples:

# Search by topic
${CLAUDE_PLUGIN_ROOT}/bin/granola.js search "product review"

# Search by person
${CLAUDE_PLUGIN_ROOT}/bin/granola.js search "john@example.com"

Export to Markdown

${CLAUDE_PLUGIN_ROOT}/bin/granola.js export <meeting-id> [--output DIR]

Exports a meeting to a markdown file with YAML frontmatter, notes, and transcript.

Examples:

# Export to default directory
${CLAUDE_PLUGIN_ROOT}/bin/granola.js export 02b2432a

# Export to specific directory
${CLAUDE_PLUGIN_ROOT}/bin/granola.js export 02b2432a --output ./meetings

List Folders

${CLAUDE_PLUGIN_ROOT}/bin/granola.js folders

Lists all meeting folders with the number of meetings in each.

Show Folder Contents

${CLAUDE_PLUGIN_ROOT}/bin/granola.js folder <folder-id>

Lists all meetings in a specific folder. Use partial IDs.

Examples:

# List folders first
${CLAUDE_PLUGIN_ROOT}/bin/granola.js folders

# Show meetings in a folder
${CLAUDE_PLUGIN_ROOT}/bin/granola.js folder a65b47fc

Common Workflows

"What did we discuss in yesterday's meeting?"

1. List recent meetings to find the ID
2. Show the meeting with notes and transcript

${CLAUDE_PLUGIN_ROOT}/bin/granola.js list --days 2
${CLAUDE_PLUGIN_ROOT}/bin/granola.js show <id> --transcript

"Find all meetings with John about the project"

${CLAUDE_PLUGIN_ROOT}/bin/granola.js search "John"
${CLAUDE_PLUGIN_ROOT}/bin/granola.js show <id>

"Export last week's meetings for the report"

${CLAUDE_PLUGIN_ROOT}/bin/granola.js list --days 7
# Export each relevant meeting
${CLAUDE_PLUGIN_ROOT}/bin/granola.js export <id1> --output ./weekly-report
${CLAUDE_PLUGIN_ROOT}/bin/granola.js export <id2> --output ./weekly-report

Output Format

• List: Markdown-formatted list with meeting title, ID, date, and participants
• Show: Full markdown document with metadata, summary, overview, notes, conferencing info, and optional transcript
• Search: Condensed list of matching meetings
• Export: Markdown file with YAML frontmatter for use in Obsidian, Notion, etc.
• Folders: List of folders with meeting counts

Limitations

• Only works on macOS (where Granola stores its cache)
• Reads from local cache - may not include very old meetings
• Transcript availability depends on meeting recording settings