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

# Granola

Discover Granola workspace members and roles, and track sign-ins and meetings recorded per user, from Granola's Enterprise Audit API

Granola is an AI meeting-notes app. The Granola integration connects your Granola workspace to Harmony as an AI category integration. Once connected, Harmony reads your workspace's audit log to show who is a member, who signs in, and who records meetings, so unused seats show up alongside your other tools.

{% hint style="warning" %}
**Requires Granola Enterprise.** Granola exposes workspace members and activity only through its Audit API, which is available on the Enterprise plan. Business and Basic workspaces cannot connect this integration. Their Granola usage can still appear in Harmony through sign-in discovery from your identity provider.
{% endhint %}

### What the Granola integration enables

| Capability       | Description                                                                                       |
| ---------------- | ------------------------------------------------------------------------------------------------- |
| Member Discovery | Surface the members of your Granola workspace in Harmony's inventory, with email, role and status |
| Role Visibility  | See which members are Granola workspace admins                                                    |
| Sign-in Activity | See when each member signs in to Granola, how (SSO or Google/Microsoft), and from which client    |
| Meeting Usage    | Track the meetings each member records with Granola, so members who stopped using it stand out    |

### Prerequisites

1. **Granola Enterprise plan** - the Audit API is available on Enterprise only
2. **Granola workspace admin** - only admins can create Audit API keys
3. **A Harmony account** with admin privileges, on a Harmony workspace hosted in the US. The Granola integration is not yet available to workspaces hosted in the EU

### Credentials

The Granola integration uses a single **Audit API key**. Granola offers several kinds of API key, and only the Audit API key can read the audit log:

| Key type           | What it can access                                               | Works with Harmony |
| ------------------ | ---------------------------------------------------------------- | ------------------ |
| Personal API key   | Notes its owner can access, within the scopes chosen for the key | No                 |
| Workspace API key  | Notes shared to the whole workspace and opted-in spaces          | No                 |
| **Audit API key**  | The workspace audit log, and nothing else                        | **Yes**            |
| Legal hold API key | Placing and releasing legal holds                                | No                 |

An Audit API key belongs to the workspace rather than to the admin who created it, so it keeps working after that admin leaves. It cannot read notes, transcripts, folders or spaces.

### Connecting Granola to Harmony

#### Step 1: Create an Audit API key in Granola

1. In the Granola desktop app, click your workspace name in the bottom-left corner and select **Settings**
2. Open **Connectors**, then **Audit API keys**
3. Create a new key and give it a descriptive name (for example, `Harmony Integration`)
4. Copy the key

{% hint style="info" %}
A Granola workspace can hold up to **five** active Audit API keys, so Harmony can have its own key and you can revoke it on its own.
{% endhint %}

#### Step 2: Enter the key in Harmony

1. In Harmony, go to **Settings → Integrations**
2. Find **Granola** under **AI** (or search for it by name) and click its card
3. Paste the key into the **Audit API key** field
4. Click **Connect**

{% hint style="info" %}
Harmony checks the key when you save it by reading one entry from Granola's audit log. If Granola rejects the key, the save fails with an error explaining which key to use; a Personal or Workspace key pasted by mistake is expected to fail this way too. If Granola is busy or unreachable at that moment, the key is saved without the check; if it turns out to be wrong, no Granola data arrives (see Troubleshooting).
{% endhint %}

#### Rotating the key

Harmony doesn't let you edit the key of a connected integration. To replace it:

1. Create the new Audit API key in Granola first, so the old one keeps working until you switch
2. In Harmony, remove the Granola integration and add it again with the new key
3. Revoke the old key in Granola

Harmony allows one Granola integration per workspace, and the re-added integration continues the same Granola application in Harmony, with its members and history.

### Disconnecting Granola from Harmony

1. Log into your Harmony dashboard
2. Navigate to **Settings → Integrations**
3. Find **Granola** under **AI** and click its card
4. Click **Disconnect** and confirm when prompted

Once disconnected, Harmony stops syncing data from Granola. Previously synced data remains available in Harmony. You can also revoke the Audit API key in Granola under **Settings → Connectors → Audit API keys**.

### What Harmony Syncs from Granola

| Data              | Description                                                                                                                                                                  |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Members           | Email, Granola role (Admin or Member), status (active, invited or deactivated) and last sign-in, for members found in the audit log Granola has kept (at most a year)        |
| Sign-in activity  | Each sign-in to Granola, with the sign-in method (SSO, Google or Microsoft), platform, client version, IP address and approximate location as reported by the Granola client |
| Meetings recorded | One usage event per meeting a member records, credited to the member who recorded it, with whether the meeting was on their calendar                                         |

Harmony does not sync member names, departments, job titles or license details. Granola's audit log does not include them.

{% hint style="info" %}
**Sync frequency:**

* **Members** refresh once a day. On a large workspace a refresh can take several hours to read, and a refresh that cannot finish within three days is abandoned (see "The member list never appears" under Troubleshooting)
* **Sign-ins** and **meetings recorded** are collected every hour
  {% endhint %}

{% hint style="warning" %}
**How Harmony finds your members:**

Granola has no API that lists workspace members. Harmony builds the member list from your audit log: anyone who joined, was added, was invited, changed role or status, or signed in. Granola keeps at most one year of audit history, and only from when it began logging: earlier history is never backfilled, so a workspace's log may reach back much less than a year. So:

* A member with no membership change and no sign-in in the audit log Granola has kept does not appear, even if they still record meetings. Their meetings still count as usage.
* A member's role comes from their most recent role change in the log. An admin whose last role change is older than the log appears as a member.
* Members whose email the log does not record are not listed.
  {% endhint %}

{% hint style="info" %}
**Historical data on first connection:**

Sign-ins and meetings recorded are collected from up to **90 days** before you connect, and only as far back as Granola has logged. On a large workspace Harmony may collect only the most recent part of that backfill (for sign-ins, about the newest 6,000); collection after you connect is not affected. Members are built from all the audit log Granola has kept.
{% endhint %}

### Use Cases

<details>

<summary>Unused Seats</summary>

See which Granola members have stopped recording meetings, using each member's most recent recorded meeting, so you can reclaim seats in Granola. Harmony sees sign-ins and recorded meetings only: a member who only reads shared notes, uses chat, or reaches Granola through MCP, without signing in or recording, can look unused.

</details>

<details>

<summary>Access Review</summary>

Review who is a member of your Granola workspace and who holds the Admin role. Admins whose last role change is older than Granola's audit log appear as members, so confirm admin access in Granola as well.

</details>

<details>

<summary>Offboarding</summary>

Confirm that people who left your company have also left or been removed from your Granola workspace.

</details>

### Troubleshooting

<details>

<summary>Saving the integration fails with a validation error</summary>

**Possible causes:**

* The key is a Personal or Workspace API key instead of an Audit API key
* The key was revoked in Granola
* Extra spaces or characters were copied along with the key
* Your Granola workspace is not on the Enterprise plan, or its API access controls turn off the audit log
* Your Granola workspace restricts API access by IP address

**Solutions:**

1. In Granola, create a key under **Settings → Connectors → Audit API keys** and paste it into Harmony
2. Confirm the key is still listed as active in Granola
3. If your workspace restricts API access by IP address, contact Harmony support for the addresses to allow

</details>

<details>

<summary>There is no Audit API keys option in Granola</summary>

**Possible causes:**

* Your Granola workspace is not on the Enterprise plan
* You are not a workspace admin in Granola

**Solutions:**

1. Verify your plan with Granola
2. Ask a Granola workspace admin to create the key

</details>

<details>

<summary>Some members are missing</summary>

**Possible causes:**

* The member has had no membership change and no sign-in in the audit log Granola has kept (see "How Harmony finds your members" above)
* The member list has not refreshed yet - it refreshes once a day

**Solutions:**

1. Wait for the next refresh after connecting
2. If a member who uses Granola daily is still missing, contact Harmony support

</details>

<details>

<summary>The member list never appears</summary>

**Possible causes:**

* Your workspace's audit history is too large for Harmony to read within one refresh's limit. Harmony publishes a member list only when it has read the whole log, so that members are never removed because of a partial read

**Solutions:**

1. Contact Harmony support. Sign-ins and meetings recorded continue to sync in the meantime

</details>

<details>

<summary>The integration worked and then started failing</summary>

**Possible causes:**

* The Audit API key was revoked in Granola
* Your Granola workspace moved off the Enterprise plan
* Your Granola workspace started restricting API access by IP address

**Solutions:**

1. Create a new Audit API key, then remove the Granola integration in Harmony and add it again with the new key (see "Rotating the key" above)
2. Confirm your Granola plan with Granola
3. If your workspace restricts API access by IP address, contact Harmony support for the addresses to allow

</details>

### Data & Privacy

<details>

<summary>Key privacy principles</summary>

For information about how Harmony handles your data, see our [Privacy Policy](https://harmony.io/privacy).

* Harmony accesses Granola in read-only mode and does not change anything in your Granola workspace
* Harmony reads only the audit log. An Audit API key cannot read notes, transcripts or summaries, and Harmony never accesses meeting content
* From the audit log, Harmony keeps only membership changes, sign-ins and meetings recorded. Sign-in details such as IP address and location are reported by the Granola client and are not verified by Granola
* Granola's API allows 5 requests per second per workspace, shared with your other keys. Harmony paces its requests to leave room for them
* Access can be revoked at any time by revoking the Audit API key in Granola or disconnecting the integration in Harmony

</details>


---

# 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.harmony.io/integrations/ai/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.
