Granola

Status: Available (Pipedream broker connector) Ingests your Granola meetings from Granola’s public REST API (public-api.granola.ai) — one record per meeting, its AI summary (summary_markdown) as the searchable body, the meeting title as the --in container. Notes are hydrated with ?include=transcript, so attendees and the transcript ride in the record’s payload. Granola isn’t a native Pipedream app (its registry entry is an auth-only stub with no proxy domains), so this rides the broker connector: your grn_ API key lives in Pipedream, and requests proxy through it with the key injected server-side — the key never touches this machine.

# get a Granola API key from Granola → Settings → API (a grn_… key)
duckbrain connect granola      # opens the broker key-entry form; paste the grn_ key (stored in Pipedream)
duckbrain sync granola         # pull meetings → brain, searchable

duckbrain search "pricing decision" --source granola --since 30d
duckbrain context "beyond sprint planner" --on 2026-07-21

Facet	Value
`--source`	`granola`
`--in`	meeting title
`map.text`	`summary_markdown` (the meeting’s AI summary; falls back to `summary_text`)
pagination	opaque body cursor (`?cursor=`); `created_after` for incremental sync

Why not the desktop crawler? An earlier adapter used the local graincrawl archive. Granola 7.4x keeps desktop state encrypted-only and relocated the decryption key from storage.dek into the macOS Keychain (graincrawl#43), which graincrawl can’t yet unlock. The public API needs none of that — a static grn_ key, no local decryption — so the connector supersedes the crawler.

Get Started

Commands

Ingest Sources

Guide

Facet mapping

​Facet mapping

Facet mapping