Skip to main content
The Granola integration posts Granola meeting summaries into Pike. Each meeting goes to one place: an Update on a customer, an Update on a project, or a comment on a task. A scope change agreed on a client call shows on the project next to its budget, and a new account lead reads past meetings on the customer instead of booking a handover call. Direction is Granola to Pike. Pike does not send anything to Granola.

Overview

Requirements

  • A Granola Business or Enterprise plan. API keys and webhooks need one of them.
  • On Enterprise, Granola admins control which key scopes members can use.
  • A Pike workspace admin to turn on the integration.

Connect Granola

Admin step

  1. Go to Workspace settings → Integrations → Granola.
  2. Click Add integration.
Only workspace admins can turn on or disconnect Granola for the workspace.

Member step

Each member adds their own personal Granola key, so Pike reads the notes that member can already see.
  1. In Granola, go to Settings → Connectors → API keys and create a key.
  2. In Pike, go to Settings → Connections.
  3. Add your Granola key.
A personal key sees notes the member owns, notes shared directly with them, and notes in private folders shared with them. On connect, Pike registers a webhook with Granola using the key. You never touch webhook settings.

Workspace key option

A Granola admin can connect one workspace key for the whole Pike workspace. Workspace keys do not expire. They only see public workspace notes and spaces with Granola API access turned on, and they never return private notes. Most client calls live in personal space, so per-member keys are the default.

Map folders

Before your meetings, map Granola folders to Pike customers or projects. Pike lists the Granola folders the connected keys can see, and an admin maps each folder to a customer or a project in the Granola integration settings. Notes in subfolders follow the parent folder’s mapping. If you do not map a folder, put a task reference or a project number in the calendar invite before the meeting. Pike reads the meeting title, so the reference travels with the note.

How Pike matches a meeting

Granola notifies Pike when a note’s first AI summary is generated, when a note is shared with a connected member, and when a summary is edited or regenerated. Pike then fetches the note with the member’s key. Granola only releases notes that have both a transcript and an AI summary, so a note still processing syncs once it is done. Pike checks these rules in order. The first match wins, and each note goes to one place.
  1. Task reference in the meeting title. A reference such as DES-42 handover in the note title or the calendar event title, matching an existing task the member can see, posts a comment on that task.
  2. Folder mapped to a project. The note posts as an Update on that project.
  3. Project number in the meeting title. A number such as 2026-0142 weekly posts as an Update on that project.
  4. Folder mapped to a customer. The note posts as an Update on that customer.
  5. External attendee domain. If an external attendee’s email domain matches a contact on exactly one Pike customer, the note posts as an Update on that customer. Pike ignores your workspace’s own domain and free email domains such as gmail and outlook. If the attendees match more than one customer, there is no match.
  6. No match. The note does not sync.
Two rules keep matches predictable:
  • Pike never guesses a task. Task comments only come from a task reference in the title.
  • A customer match never becomes a project Update, even if the customer has one active project.
Notes created before you connect do not backfill. Only new or newly shared notes sync.

What gets posted

Pike posts:
  • The meeting title.
  • The meeting date: the calendar start time, or the note creation time if there is no calendar event.
  • The attendee names.
  • The Granola AI summary.
  • A link to the full note in Granola.
Pike never posts or stores transcripts. The text the note owner typed during the meeting is included only if that member turns the option on, and it is only available with the owner’s personal key. The Update or comment shows as coming from Granola, attributed to the member whose note it was.

Duplicates and edits

  • A note posts once per workspace. If the same note is shared with several connected members, it does not post again.
  • If two members record the same calendar meeting, the second note does not create a second post in the same place. Its Granola link is added to the existing one.
  • When a summary is edited or regenerated in Granola, Pike updates the existing Update or comment and marks it edited.
  • Deleting a note in Granola does not delete it in Pike.

Privacy and visibility

Visibility follows where the note posts. An Update on a private project, or a comment on a task in one, is only visible to people who can see that project. See Private projects. The customer portal shows comments on published deliverables only. Granola Updates and task comments do not appear there. See Customer portal.

Disconnect

Disconnecting Granola stops new notes from posting and removes the webhook Pike registered with Granola. Updates and comments already posted stay in Pike. If a key is revoked in Granola, Pike marks that member’s connection as disconnected and notifies them. Add a new key under Settings → Connections to resume.

Troubleshooting

If Pike cannot be reached, Granola retries for four days. After four days of failures Granola disables the webhook and does not replay missed notes. Reconnecting in Pike restores it.

Limits

  • Requires a Granola Business or Enterprise plan.
  • Pike only receives notes the connected key can read.
  • Notes from before you connect do not backfill.
  • Notes that match nothing do not sync.
  • Task comments need a task reference in the meeting title.
  • Transcripts stay in Granola.