Granola Block

The Granola block integrates Granola into your workflow to retrieve meeting notes, summaries, attendees, and transcripts. Reach for it when you want to pull meeting context into an agent or downstream automation.

Overview

When to Use

• Fetch a list of recent meeting notes to feed into a summarization or follow-up workflow.
• Retrieve a single meeting note by its ID, including attendees, calendar event details, and the summary.
• Include the full meeting transcript when you need verbatim detail for analysis or coaching.
• Filter notes by creation or update date to scope a workflow to a specific time window.
• Paginate through large sets of notes using a cursor from a previous response.
• Drive post-meeting automation — action items, CRM updates, Slack summaries — directly from a Granola note.

Configuration

Operation

Choose what the block does. Defaults to list_notes.

API Key

Required. Your Granola API key used to authenticate requests to the Granola API.

Note ID

Required for the get_note operation. The ID of the specific note to retrieve (e.g., not_1d3tmYTlCICgjy). Only shown when operation is get_note.

Include Transcript

Advanced. For get_note, whether to include the full meeting transcript in the response. Only shown when operation is get_note.

Defaults to false.

Created After

Advanced. For list_notes, return only notes created after this date (ISO 8601, e.g., 2026-01-01). Only shown when operation is list_notes.

Created Before

Advanced. For list_notes, return only notes created before this date (ISO 8601, e.g., 2026-03-01). Only shown when operation is list_notes.

Updated After

Advanced. For list_notes, return only notes updated after this date (ISO 8601, e.g., 2026-01-01). Only shown when operation is list_notes.

Page Size

Advanced. For list_notes, number of notes to return per page (1–30, default 10). Only shown when operation is list_notes.

Cursor

Advanced. For list_notes, a pagination cursor from a previous list_notes response, used to fetch the next page. Only shown when operation is list_notes.

Inputs & Outputs

• Inputs:

  • operation (string) — Operation to perform (list_notes or get_note)
  • apiKey (string) — Granola API key
  • noteId (string) — Note ID for the get_note operation
  • includeTranscript (string) — Whether to include transcript ("true" or "false")
  • createdAfter (string) — Filter notes created after this date
  • createdBefore (string) — Filter notes created before this date
  • updatedAfter (string) — Filter notes updated after this date
  • pageSize (number) — Results per page (1–30)
  • cursor (string) — Pagination cursor

• Outputs:

  • notes (json) — List of meeting notes (returned by list_notes)
  • hasMore (boolean) — Whether more notes are available (returned by list_notes)
  • cursor (string) — Pagination cursor for the next page (returned by list_notes)
  • id (string) — Note ID (returned by get_note)
  • title (string) — Note title (returned by get_note)
  • ownerName (string) — Note owner name (returned by get_note)
  • ownerEmail (string) — Note owner email (returned by get_note)
  • createdAt (string) — Creation timestamp
  • updatedAt (string) — Last update timestamp
  • transcript (json) — Meeting transcript entries, if requested (returned by get_note)

Tools

• Granola List Notes (granola_list_notes) — Calls GET https://public-api.granola.ai/v1/notes to list meeting notes with optional date filters (createdAfter, createdBefore, updatedAfter) and pagination (pageSize, cursor). Returns notes, hasMore, and cursor.
• Granola Get Note (granola_get_note) — Calls GET https://public-api.granola.ai/v1/notes/{noteId} to retrieve a single note by ID. Optionally includes the full transcript when includeTranscript is "true". Returns note metadata, summary, attendees, calendar event details, and optionally the transcript.

YAML Example

granola_1:
  type: granola
  name: "Granola"
  inputs:
    operation: "list_notes"
    apiKey: "{{GRANOLA_API_KEY}}"
    pageSize: 10
    createdAfter: "2026-01-01"
  connections:
    outgoing:
      - target: agent-block-id

For a get_note example:

granola_2:
  type: granola
  name: "Fetch Meeting Note"
  inputs:
    operation: "get_note"
    apiKey: "{{GRANOLA_API_KEY}}"
    noteId: "{{trigger.noteId}}"
    includeTranscript: "true"
  connections:
    outgoing:
      - target: summarize-block-id