Repository navigation
feat: sync Granola notes through its paginated API - #248
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Granola's MCP sync exposes an unpaginated 30-day listing. API access lets Context Use backfill older meeting notes and resume through native pagination.
How
Use Granola's REST API with API-key authorization and durable page checkpoints. Keep the existing sync and document UUIDs so backfills update existing records, preserve pause state, and retain notes that disappear upstream. Replace OAuth setup with an API-key form and use open-sync 0.5.1 for connection replacement.
Existing users save a Granola API key under Authorization to start the backfill.