Skip to main content
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.

Book a demo

See how teams govern agents that use Granola.

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 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.

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 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 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 for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the granola_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~granola:

Frequently asked questions

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.
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.
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 for details.
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

Book a demo

See how teams govern agents that use Granola.

Talk to sales

Get access to Guild, then connect Granola to your first agent.
Also runs on Guild: Calendly · Coda · Confluence · Fathom Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026