Digest voice-of-customer notes from Granola
Connect Granola with your own account and prepare a weekly digest of customer themes from one folder of meeting notes.
The Granola voice-of-customer digest template reads the past week's
meeting notes and transcripts in one folder and distills them into recurring
customer pain points, feature requests, objections, and praise, quoting short
excerpts attributed to the meeting and date and separating what customers said
from interpretation. It follows the customer-research marketing skill:
quote evidence, never invent sentiment, and end with the follow-ups most worth
human attention.
Enable and connect Granola
An operator must enable MANAGED_MCP_GRANOLA_ENABLED. Granola's authorization
server at mcp-auth.granola.ai supports dynamic client registration, so no
static client is needed; connect the Granola card and sign in with your own
Granola account. Each person authenticates individually — there is no
workspace-wide grant — and Granola's plan and folder-sharing limits decide
which notes the token can reach, so share the folder the routine should read
with the authorizing account.
Set the variable
| Key | Example | Why it is a variable |
|---|---|---|
noteFolder | Customer calls | Which folder holds customer conversations varies per team, and it is also the routine's read boundary. |
Reference it in the instructions as {{noteFolder}}.
Current beta boundary
Granola is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. Meeting notes routinely contain personal data and confidential discussion, which is why even reads stay blocked until the review lands; the reviewed manifest should cover note and folder reads only, and the routine's instructions already forbid reading outside the configured folder and editing, sharing, or deleting any note.
Recovery
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.
Because grants are per person, the connection follows the account that
authorized it; if that person leaves, reconnect with another account that has
access to the same folder.