Skip to content

Add Granola Sync plugin (dannymcc.GranolaSync)#739

Open
dannymcc wants to merge 1 commit intoNotePlan:mainfrom
dannymcc:add-granola-sync-plugin
Open

Add Granola Sync plugin (dannymcc.GranolaSync)#739
dannymcc wants to merge 1 commit intoNotePlan:mainfrom
dannymcc:add-granola-sync-plugin

Conversation

@dannymcc
Copy link

Summary

  • Adds Granola Sync, a plugin that syncs Granola AI meeting notes into NotePlan
  • Syncs meeting notes with configurable content sections (personal notes, AI-enhanced notes, transcripts)
  • Integrates with daily, weekly, and monthly calendar notes
  • Supports attendee tagging, Granola folder mirroring, and flexible filename templates
  • Based on the Granola Sync Plus for Obsidian plugin

Commands

Command Description
Sync recent notes from Granola AI Sync recent meetings up to configured limit
Sync ALL historical notes from Granola AI Sync all historical meetings
Find duplicate Granola notes Scan vault for duplicate Granola IDs

Source repository

https://github.com/dannymcc/Granola-to-NotePlan

Syncs Granola AI meeting notes into NotePlan with configurable content
sections, attendee tags, folder mirroring, and daily/weekly/monthly
calendar note integration.
@jgclark
Copy link
Collaborator

jgclark commented Mar 6, 2026

Hi Danny, I've had a quick look at the code, and I can see that this fits well with the existing NotePlan plugin architecture. Good work!

You actually now have a choice: it become an official plugin, or the first of a new class of wider community plugins. Either way it should be listed as one that can be installed from inside NP.
For the first, you would need to commit to supporting it for at least a year. One of us volunteers would then look it over in more detail, and when happy merge this PR into the repo. When you want to make changes it would need to wait for review.
For the second, you don't need to make any commitment, and would only have a simple check made of its code, but it would live in your own repo still, and you can change whenever you wish. It would have some sort of label (yet to be determined), that indicates it's in this wider category, and potentially less polished or maintained.

I assume it can become an official plugin: is that what would you prefer?

@dannymcc
Copy link
Author

H @jgclark - happy to commit to the updates and become an official plugin.

@jgclark
Copy link
Collaborator

jgclark commented Mar 13, 2026

OK, thanks.
Action is now with Eduard, who will use this as a test case for running some automated (rather than further volunteer) checks on submissions, and then (I'm sure) add as an official plugin.

@EduardMe
Copy link
Contributor

@dannymcc happy to add it, we are currently discussing how we can support community plugins that are outside the main repo, so that you won't have to PR in an update every time, to reduce the friction.

We were thinking about adding a community plugin json file to the repo that points to the repo of the plugin. I think the easiest for NotePlan would be if you create a release on GitHub with the script and plugin.json files added as attachments, so NotePlan knows what to download.

We will add a community_plugins.json file with the repo url, title, author, etc., NotePlan picks the release from that repo.

This way you can make updates independently.

@jgclark
Copy link
Collaborator

jgclark commented Mar 13, 2026

Good news. As expected, the plugin has passed some safety and quality tests.
The only suggestion is that

The instructions are in the README only. Once the plugin is installed in NotePlan, users interact with it through the plugin settings panel, and there's no in-app guidance pointing them to that file path. If someone installs the plugin without reading the README first and tries to run a sync, the code does show an error message when the token is missing — but it doesn't tell them where to find the token.

So we suggest you just make that small tweak, and then we will publish it to the repo, which will then straight away make it available within the app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants