How dannymcc/granola-to-obsidian works
Project type and purpose
• This is an Obsidian Community Plugin (“Granola Sync”) that runs inside the Obsidian host, fetches meeting notes from the external Granola AI service, converts them to Markdown, and writes them into your vault with rich metadata and integrations.
File structure
• Top‐level files only:
• main.js – plugin entrypoint, loads settings, registers commands, scheduler, and handlers
• manifest.json – plugin metadata (id, version, name, commands) used by Obsidian
• styles.css – custom CSS for status bar and ribbon UI elements
• versions.json – tracks plugin release versions
• .github folder contains CI/workflow for automated releases.
• No nested source folders: logic is modularized within main.js (or imported modules if built).
Key insights from the README
• Core features: auto/manual sync, customizable filename/date templates, daily‐note & periodic‐note integration, attendee tagging, smart update handling, Granola URL linking.
• Uses Obsidian Plugin API for scheduling, commands, settings screen, file I/O, and UI updates.
• Reads a local auth file (supabase.json) to authenticate against Granola API.
Details to capture
• Plugin lifecycle hooks (onload → registers commands & scheduler, onunload → clean up)
• Settings → Configurable folder path, templates, auth path
• Scheduler intervals (1min → daily)
• Error & success flows back to the status bar
• Distinct modules rather than lumped together for clarity