How do I integrate Granola with Pylon?

Last updated: September 8, 2026

Before you begin: You must be a Granola workspace admin on a Business or Enterprise plan. Pylon requires a Granola workspace API key; Personal API keys are not supported.

Follow Granola’s instructions to create a workspace API key, and make sure to copy the key when it is generated.

  1. Go to the Apps Directory in Pylon.

  2. Open the Granola app and click Connect.

  3. Paste the workspace API key from Granola into Pylon and click Authorize.

Once connected, eligible Granola calls will begin to backfill into Pylon. New calls and later edits will also sync automatically.

What gets synced?

  • Pylon syncs completed public notes and notes in API-enabled Granola workspace folders, including their transcripts and meeting metadata.

  • Private notes that have not been shared to an accessible workspace location will not sync.

  • Granola only makes notes available through the API after they have a generated summary and transcript. Notes that are still processing or were never summarized will not appear in Pylon.

Historical call backfill

When you connect your Granola workspace API key, Pylon automatically backfills existing eligible notes. You do not need to move historical calls into a special Zapier folder.

Switching from Zapier

Switching from Zapier to the API may pull more calls into Pylon. The API syncs every eligible completed note visible to the workspace API key, rather than only calls sent through your Zapier setup.

If your Granola integration is currently connected through Zapier, we recommend switching to the API. Click Switch to API on the Granola integration page and authorize with a workspace API key. After the API connection succeeds, disable your old Granola-to-Pylon Zap. The API integration becomes authoritative, and Pylon will no longer accept deliveries from the legacy Zapier flow.

Legacy Zapier setup

The legacy integration requires a Granola Business or Enterprise plan and a Zapier account.

  1. Go to the Apps Directory in Pylon.

  2. Open the Granola app and choose the Zapier connection option.

  3. Log in to Zapier and complete the Granola-to-Pylon template.

  4. Connect your Granola account to the first block. Choose either Note added to folder or Note shared with Zapier as the trigger.

    • For the folder trigger, select the Granola workspace and folder to watch. Recurring meetings can be added to that folder automatically, but non-recurring notes must be moved there manually.

    • For the manual-share trigger, you do not need to select a folder.

  5. In the Pylon step, sign in to Pylon and enter a Pylon API token.

  6. Publish the Zap.

Once a Granola note is sent through Zapier, it appears on the Apps Directory → Granola page and becomes available throughout Pylon.

Historical calls: Zapier does not automatically backfill older Granola notes. With the folder trigger, you may ingest an older note by manually moving it into the watched folder.

Legacy recording limitations: Zapier deliveries may not include specific speaker names, per-message timestamps, or an accurate call duration.