> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Read Granola meeting notes and manage webhooks from Guild agents

> Connect Guild agents to Granola to retrieve meeting notes, page through transcripts, manage folders, track audit events, and configure webhook endpoints.

Integrations · Granola

Guild agents read meeting notes and transcripts from Granola and react to note lifecycle events through webhooks. Guild stores your Granola API key server-side so agent code never sees it. Credential policies let you restrict which operations each agent can perform, and every request is logged for audit.

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Granola.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Granola to your first agent.

## What the Granola integration exposes

The integration gives agents tools to list and retrieve meeting notes that have a generated AI summary and transcript, and to page through transcripts that exceed a single response. Agents can list and manage folders, list audit events, and register, update, delete, and list webhook endpoints. The inbound tool handles note.generated, note.edited, and note.access\_granted events.

## How it works

**1. Open your credentials page**

In Guild, go to Access & setup > Credentials. See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped options.

**2. Connect the Granola integration**

Click Connect, select granola, and paste your API key into the API Key field. Guild sends the key as a bearer token in the Authorization header.

**3. Add tools to your agent**

Import GranolaTools from the integration package and spread it into your agent's tools object. Use pick() to include only the tools your agent needs, as described in [Tool sets](https://docs.guild.ai/sdk/tools.md).

## Why Granola access needs governing

Meeting notes and transcripts can contain sensitive information from internal discussions. Guild's credential proxy holds the Granola API key server-side, so agents never receive the raw secret. You can scope a credential to one workspace, one team member, or a single agent using the options on the [Credentials](https://docs.guild.ai/platform/credentials.md) page, which prevents other workspaces from using it.

Credential policies let you write ALLOW and DENY rules that the proxy enforces before any request reaches Granola. You can restrict an agent to read-only tools such as granola\_list\_notes and granola\_get\_transcript while blocking webhook registration tools entirely. The granola\_list\_audit\_events tool gives you a record of activity to review. See [Credential policies](https://docs.guild.ai/platform/credential-policies.md) for rule syntax and enforcement details.

## About the Granola integration

Agents can list, retrieve, and page through meeting notes and transcripts stored in Granola. They can organize content via folders and monitor activity through audit events. Agents can also register, update, and delete webhook endpoints to react to note lifecycle events in real time. The integration is `guildai~granola`.

## Authentication

* **Type:** API key
* **Header:** Guild sends the key as a bearer token in the `Authorization` header

### Setup

**1. Connect Granola**

In Guild, go to **Access & setup > Credentials**, click **Connect**, select **granola**, and paste the key into **API Key**.

See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped credentials.

## Usage

```typescript theme={null}
import { GranolaTools } from "@guildai-services/guildai~granola"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  systemPrompt: "You work with Granola.",
  tools: { ...GranolaTools },
})
```

### Selecting specific tools

Tools are named with the `granola_` prefix. Use [`pick()`](https://docs.guild.ai/sdk/tools#selecting-specific-tools) to include only what your agent needs.

## Tools

Tools in the latest published version of `guildai~granola`:

| Tool | What it does |
| - | - |
| `granola_create_webhook_endpoint` | Register an HTTPS URL to receive note events. signing\_secret is returned only in this response. |
| `granola_delete_webhook_endpoint` | Delete webhook endpoint |
| `granola_get_note` | Retrieve one meeting note by not\_ ID. include=transcript may return 413 TRANSCRIPT\_TOO\_LARGE; then call get\_transcript. |
| `granola_get_transcript` | Retrieve a meeting transcript in pages. |
| `granola_list_audit_events` | List audit events |
| `granola_list_folders` | List folders |
| `granola_list_notes` | List accessible meeting notes that already have a generated AI summary and transcript. |
| `granola_list_webhook_endpoints` | List webhook endpoints |
| `granola_receive_note_event` | Inbound Guild hook for note.generated, note.edited, and note.access\_granted. |
| `granola_update_webhook_endpoint` | Update webhook endpoint |

## Frequently asked questions

> [accordion] Can an agent get a full transcript in one call?
>
> Not always. Calling granola\_get\_note with include=transcript may return a 413 TRANSCRIPT\_TOO\_LARGE error. When that happens, the agent calls granola\_get\_transcript to retrieve the transcript in pages.

> [accordion] Where is my Granola API key stored?
>
> Guild stores it as a credential and injects it server-side as a bearer token in the Authorization header. Agent code never sees the key.

> [accordion] Can I limit which Granola tools a specific agent can use?
>
> Yes. Write credential policies with ALLOW and DENY rules scoped to a specific agent. The proxy enforces the rules before any request reaches Granola. See [Credential policies](https://docs.guild.ai/platform/credential-policies.md) for details.

> [accordion] Does the integration receive webhook events automatically?
>
> No. The catalog entry shows no built-in webhook events. To receive note lifecycle events, an agent must register an HTTPS endpoint using granola\_create\_webhook\_endpoint. The signing\_secret is returned only in that initial response.

## Put a governed agent on Granola this week

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Granola.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Granola to your first agent.

## Related

**Also runs on Guild:** [Calendly](https://docs.guild.ai/integrations/calendly.md) · [Coda](https://docs.guild.ai/integrations/coda-openapi.md) · [Confluence](https://docs.guild.ai/integrations/confluence.md) · [Fathom](https://docs.guild.ai/integrations/fathom.md)

**Read:** Docs: [Credential policies](https://docs.guild.ai/platform/credential-policies.md) · [Credentials](https://docs.guild.ai/platform/credentials.md) · [Tools in agents](https://docs.guild.ai/sdk/tools.md)
