1. Before you start
- Confirm the Granola workspace is on a Business or Enterprise plan with API access.
- Create a personal key for your own visible notes or ask a Granola administrator to create a workspace key for public and API-enabled spaces.
- Choose the matching personal or workspace scope in Seedling.
- Do not send Granola credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
2. Connect Granola
- In Granola Settings > Integrations, create the appropriate API key.
- In Seedling, open Connections, select Granola, and choose personal or workspace scope.
- Paste the grn_ API key, add an optional account name, and connect.
- Allow the initial 365-day note import and folder-context refresh to complete.
3. Authorization and connection problems
- API key rejected
- Confirm the key begins with grn_, remains active, and belongs to an account with Granola API access.
- Note not returned
- Confirm the note is visible to the key and has both an AI-generated summary and transcript.
- Workspace note remains system-only
- This is expected: the API does not provide complete per-note human ACLs, so Seedling fails closed.
4. Missing or delayed data
- Confirm the note falls within the initial history window or has been updated since the current cursor.
- Confirm the key can still see the note and its transcript has not been removed by Granola retention settings.
- Do not treat a missing list result or detail 404 as proof of deletion; processing, eligibility, and access changes can also make a note disappear.
- Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
- If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.
5. Rotate or replace access
Never use email or an ordinary support ticket to transfer the old or replacement credential.
- Disconnect the existing Granola connection and wait for its purge to finish.
- Create the replacement key in Granola and reconnect it with the intended personal or workspace scope.
- Revoke the previous key in Granola after the replacement is verified.