Granola connector
Set up the Granola connector in Kaivo: authentication, configuration, the 2 BigQuery tables it syncs, and answers to common questions.
Granola connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Granola data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your data from Granola instead of moving it.
What is the Granola connector
Section titled “What is the Granola connector”Sync your Granola meeting notes into BigQuery with Kaivo to analyse and search your notes alongside the rest of your data.
| Category | Other |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Granola connector
Section titled “Getting started with the Granola connector”- Sign up for Kaivo and create a workspace.
- Connect your Granola account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Granola
Section titled “Authenticating Granola”Authenticate with your API Key.
| Field | Description |
|---|---|
| API Key | |
| Your Granola API key. Find it in the Granola app under Settings > Connectors > API keys (personal) or Settings > API (Enterprise). |
|
Configuring the Granola connector
Section titled “Configuring the Granola connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Start Date | |
| Any data before this date will not be fetched. |
|
Tables and columns synced from Granola
Section titled “Tables and columns synced from Granola”Kaivo syncs 2 tables from Granola into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
detailed_notes (16 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
STRING |
The unique identifier of the note. |
object |
STRING |
The object type, always “note”. |
title |
STRING |
The title of the note. |
owner__name |
STRING |
The name of the note owner. |
owner__email |
STRING |
The email address of the note owner. |
created_at |
TIMESTAMP |
The creation time of the note in ISO 8601 format. |
updated_at |
TIMESTAMP |
The last update time of the note in ISO 8601 format. |
calendar_event__event_title |
STRING |
Title of the calendar event. |
calendar_event__organiser |
STRING |
Email of the event organiser. |
calendar_event__calendar_event_id |
STRING |
Calendar event identifier. |
calendar_event__scheduled_start_time |
TIMESTAMP |
Scheduled start time of the event. |
calendar_event__scheduled_end_time |
TIMESTAMP |
Scheduled end time of the event. |
summary_text |
STRING |
Plain text summary of the note. |
summary_markdown |
STRING |
Markdown formatted summary of the note. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: detailed_notes__calendar_event__invitees
Section titled “Subtable: detailed_notes__calendar_event__invitees”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
email |
STRING |
Email of the invitee. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: detailed_notes__attendees
Section titled “Subtable: detailed_notes__attendees”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
name |
STRING |
Name of the attendee. |
email |
STRING |
Email of the attendee. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: detailed_notes__folder_membership
Section titled “Subtable: detailed_notes__folder_membership”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
STRING |
Unique folder identifier. |
object |
STRING |
Object type (folder). |
name |
STRING |
Name of the folder. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: detailed_notes__transcript
Section titled “Subtable: detailed_notes__transcript”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
speaker__source |
STRING |
Source of the speaker (microphone or speaker). |
text |
STRING |
Transcript text content. |
start_time |
TIMESTAMP |
Start time of the transcript segment. |
end_time |
TIMESTAMP |
End time of the transcript segment. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
notes (8 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
STRING |
The unique identifier of the note. |
object |
STRING |
The object type, always “note”. |
title |
STRING |
The title of the note. |
owner__name |
STRING |
The name of the note owner. |
owner__email |
STRING |
The email address of the note owner. |
created_at |
TIMESTAMP |
The creation time of the note in ISO 8601 format. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Granola sync works
Section titled “How the Granola sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Granola supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Granola?
Section titled “How long does the initial sync take for Granola?”It depends on how much history is in your Granola account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Granola’s schema changes?
Section titled “What happens when Granola’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Granola, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Granola instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Granola connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Granola data
Section titled “Common use cases for Granola data”Notes search
Section titled “Notes search”Use notes and detailed_notes to search and analyse what was discussed across meetings.
Theme analysis
Section titled “Theme analysis”Bring notes into BigQuery to extract recurring topics and action items.
Combine with other data
Section titled “Combine with other data”Join notes with your CRM data to connect meetings to accounts.
Use Granola data in your AI and BI tools
Section titled “Use Granola data in your AI and BI tools”Once Granola data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Granola data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Granola connector pricing and plan details.
Related connectors
Section titled “Related connectors”- Demo: Sync Demo to BigQuery.
- Care Quality Commission: Sync Care Quality Commission to BigQuery.
- DingConnect: Sync DingConnect to BigQuery.
- CIMIS: Sync CIMIS to BigQuery.
- Navan: Sync Navan to BigQuery.
- Eventbrite: Sync Eventbrite to BigQuery.