AI workers for Granola
Ready-made AI workers for Granola: meeting notes turned into filed follow-ups, decisions extracted while they are still accurate, and commitments that survive the walk back to your desk.
- Meeting Prep Assistant
Builds a prep sheet for each meeting on your calendar: who, history, open items, and talking points.
- CRM Scribe
Logs your meetings and email threads into the CRM so records stay current without manual data entry.
- Meeting Action Item Collector
Reads your meeting notes each evening and files every action item into your task board.
- Post-Meeting Closer
Reads today's meeting notes, extracts owners and asks, then leaves follow-up email drafts — never posts or books.
- Adoption Meeting Review
Explains customer adoption blockers and commitments from recent meeting notes.
- Customer Success Plan Workflow
Combines account outcomes and customer meeting evidence into a reviewable success plan.
- Customer Problem Evidence Review
Extracts customer problems and contrary evidence from product discovery meetings.
- Product Opportunity Brief Workflow
Connects customer problem evidence with roadmap commitments to draft a product opportunity brief.
- Deal Objection Evidence Review
Explains buyer objections and unanswered discovery questions from sales meeting evidence.
- Sales Coaching Preparation Workflow
Combines buyer objections and approved material into a practical coaching session plan.
What is an AI worker for Granola?
An AI worker for Granola is an AI agent scoped to one job on your meeting notes, such as turning what was agreed into tasks in your tracker or reporting the decisions taken across a week of calls. It reads the notes you scope it to, and the full transcript is a separate permission on top, so a worker can work from summaries without ever opening the verbatim record.
What these workers do
Turn commitments into filed tasks
Reads what people agreed to do and creates the follow ups in your tracker with owners attached, while the context is still fresh enough to be right.
Report the decisions from a week of calls
Reads across recent meetings and returns what was actually decided, separated from what was merely discussed.
Brief someone who missed the meeting
Turns the notes into a short summary aimed at a person who was not there, covering what changed and what is now expected of them.
Flag questions nobody answered
Surfaces the open questions raised in meetings and never resolved, which is where most quietly dropped work begins.
How an AI worker runs in Granola
Notes and transcripts are separate permissions
The gap between the meeting and the follow-through
A week reads differently from a meeting
Granola questions, answered.
Does an AI worker read my full meeting transcripts?
Only if you grant transcript access, which is a separate permission from notes and is off unless you turn it on. Most jobs work from the notes alone, so the verbatim record can stay closed while follow-ups still get filed.
Which meetings can it see?
The ones inside the scope you set, including how far back it may look. You can keep a worker to recent meetings only, so an old and sensitive call is not in reach of a worker built for this week's follow-ups.
Can it write back into my notes?
Notes are typically connected read only, with the worker's output going to your tracker, your inbox, or a chat channel instead. That keeps the record of what was said as the humans in the room left it.
What if the notes are ambiguous about who owns something?
A well written worker flags it rather than assigning it to somebody. An unclear commitment turned into a confidently assigned task is worse than an open question, because it looks handled and therefore stops being discussed. The useful behaviour is to name the ambiguity and let the people who were in the room settle it.
What AI workers can do in Granola
The tools a worker can be granted in Granola once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.
List Notes
List meeting notes newest first, each with title, owner, attendees, calendar event, folders, and the AI summary (`summaryText` / `summaryMarkdown`); the verbatim `transcript` is never included here, fetch it with granola_get_transcript. Filter by date range, `folderId`, or `query` (keyword match over title and summary). Paginate with `cursor` from the response and stop when `hasMore` is false. An empty `notes` list with a non-null `accessInfo` means a token rule limited what is visible, not that none exist; render `accessInfo` verbatim.
Get Note
Get one meeting note by id with its full metadata and AI summary (`summaryText` / `summaryMarkdown`). The verbatim `transcript` is not included; use granola_get_transcript for that. Any field the token cannot see comes back null or empty with an explanatory `accessInfo`; render it verbatim.
Get Transcript
Get one meeting note including its verbatim `transcript` (an array of speaker-labelled segments) alongside the summary and metadata. The transcript is a separately governed, higher-sensitivity tier: when it is not granted the note still returns but `transcript` is null with an `accessInfo` explaining why; render that verbatim rather than treat it as an empty meeting.
List Folders
List the note folders, each with `id` (use as folderId for granola_list_notes), `name`, and optional `parentFolderId`. Paginate with `cursor` from the response and stop when `hasMore` is false.