> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/call-recording/granola.md).

# Granola

Connect Pylon to Granola to ingest call recordings.

## Setup

Granola connects to Pylon with a Granola workspace API key. Personal API keys aren't supported.

1. Click into the App Directory from your Pylon dashboard and then click on the Granola integration.
2. Click **Connect**.
3. In **Authorize Granola with a workspace API key**, paste your key into **Granola workspace API key** and click **Authorize**.

Pylon syncs public notes and notes in API-enabled workspace folders. After you connect, new notes sync automatically, and Pylon backfills existing notes that the key can access. Pylon stores the key encrypted and never displays it after you connect.

To replace the key, click **Reauthorize** and enter a new workspace API key. To stop syncing, click **Disconnect**. Call recordings that already synced stay in Pylon.

See the [Granola setup guide](https://support.usepylon.com/articles/9452304640-how-do-i-integrate-granola-with-pylon).

### Switch from Zapier

If you connected Granola through Zapier, the Granola integration shows **Switch to API**.

1. Click **Switch to API**.
2. Enter a Granola workspace API key and click **Switch to API**.
3. Disable your existing Granola Zap to finish the migration.

After the switch, Pylon stops accepting new Granola recordings from Zapier.

## Usage

Each synced Granola note that has a transcript is ingested as a call recording. When a note is edited in Granola, Pylon updates the call recording. Pylon matches it to an account using the meeting participants' email addresses, excluding your own team's.

That transcript will be used as data context for Pylon features like [Ask AI](/pylon-docs/platform/ask-ai.md), [Account Copilot](/pylon-docs/account-intelligence/accounts/copilot.md), and [Account Blocks](/pylon-docs/account-intelligence/notebooks/blocks.md), and will be visible on the activity timeline for accounts and related issues.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/integrations/call-recording/granola.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.