Documentation Index
Fetch the complete documentation index at: https://help.statisfy.com/llms.txt
Use this file to discover all available pages before exploring further.
Connect Granola with Statisfy
The Granola integration pulls AI-generated meeting notes — transcripts, summaries, attendees, and the linked calendar event — from your Granola workspace into Statisfy. Meetings are matched to the right customer account and surface alongside the rest of the activity timeline. Prerequisites:- Admin access to both Granola and Statisfy
- A Granola Workspace API key (Granola Business plan or higher)
- A connected CRM (Salesforce or HubSpot) — non-CRM integrations are gated until at least one CRM sync has completed
Only Granola Workspace API keys are supported. Personal API keys (issued to individual users) are not used by this integration.
What Gets Synced
| Data Type | Description |
|---|---|
| Meeting Notes | Granola notes with their AI-generated summary (Markdown) |
| Transcripts | Full speaker-tagged transcripts with timestamps |
| Attendees | Internal and external participants; owner is classified by email domain |
| Calendar Event | The underlying calendar event linked to each note |
Generate a Granola Workspace API Key
- Sign in to Granola as a workspace admin.
- Open the workspace settings and create a new Workspace API key. Refer to Granola’s API documentation for the latest steps.
- Copy the key — you’ll provide it to Statisfy in the next step.
Steps to Connect with Statisfy
- Log in to Statisfy.
- Navigate to Integrations → Granola → Connect and paste your Workspace API key. Credentials are stored encrypted in Google Cloud Secret Manager.
- Once connected, the bootstrap job runs a one-time historical backfill (default 30 days). Notes and their transcripts flow into Statisfy.
- The periodic sync runs every 4 hours with a 12-hour lookback window so updates to existing notes are picked up alongside new notes.
- Find synced meetings on each Account under AI Timeline → Source: Granola, or in the global Activities view filtered by source.
Sync Behavior
Time-bounded pulls:- Notes are fetched by their
updated_attimestamp so both new notes and edits to existing notes flow into Statisfy. - Notes that are still being processed by Granola (no summary and no transcript yet) are skipped and picked up on a future run.
- Note owners can sit on a non-tenant domain (for example, a workspace member sharing a note from a personal Granola account). Statisfy classifies internal vs. external attendees by email domain.
- Speaker labels in the transcript are passed through as-is — Granola does not resolve speakers to specific people.
- Statisfy honors
Retry-Afteron HTTP 429 responses and retries with backoff before failing the affected request.
- A failure on a single note does not abort the batch — other notes continue to process.
- If any note fails after retries, the overall job is marked FAILED in the integrations audit log so the failure is visible to admins.
Troubleshooting
Authentication failed
Authentication failed
- Verify the Workspace API key has not been rotated or revoked in Granola.
- Confirm you used a Workspace key, not a Personal key.
- If Statisfy detects an HTTP 401, the credential is automatically marked invalid — reconnect with a fresh key.
Meetings not appearing in Statisfy
Meetings not appearing in Statisfy
- Ensure your CRM integration (Salesforce or HubSpot) has completed at least one successful sync. Until then, Granola periodic jobs are skipped.
- Confirm the meeting’s external attendees match an existing account by email domain or CRM linkage.
- Notes are only ingested once Granola has finished processing them. Very recent meetings without a summary or transcript will appear on a later run.
Some notes are missing transcripts
Some notes are missing transcripts
- A note may have been created without recording (notes-only meetings have no transcript).
- The integration logs and skips individual note failures so a transient error on one note doesn’t block the rest. Contact support@statisfy.com with the note ID if the same note is repeatedly missing.