Turn Granola action items into Microsoft To Do tasks
When a new Granola meeting note lands, an agent picks the action items that are yours and files them as Microsoft To Do tasks with context.
Integrations
Granola
Microsoft To Do
Type
Categories
- Personal Productivity
Build me an agent workflow that turns my Granola meeting notes into Microsoft To Do tasks, but only for the action items that are actually mine.
Trigger: poll Granola for a new note. Use Granola's first-class "new note" poll trigger so the workflow fires the moment a meeting note is created.
When a new note appears, call Granola's Get Note operation for that note id and include the transcript. The agent should work from the full picture: the meeting title, date, attendees, the summary, and the transcript.
Action item selection rules. The agent should only keep items that are clearly assigned to me, or are unowned but obviously mine to handle given the context (for example, the only commitment in my area of responsibility, or something I explicitly agreed to in the transcript). It must ignore decisions, FYIs, recaps, questions, and any action items owned by other attendees. If there are no real action items at all, end the run silently. I do not want phantom tasks from every casual call.
Destination list. Call Microsoft To Do's List Task Lists to find my lists. If I have a list named "Meetings", create the tasks there. Otherwise use the default list (the one with wellknownListName defaultList). Do not create a new list on my behalf.
For each kept action item, call Create Task on the chosen list with:
- A clean one-line title that reads as a task, not a sentence from the transcript. Example: "Send Acme the updated pricing deck".
- A body that includes the meeting title, the meeting date, the attendees, and the exact line from the note (summary or transcript) that justified the task, quoted verbatim so I can audit it.
- A due date only when the note mentions one for that specific item ("by Friday", "before the next sync", "end of month"). If no date is mentioned, leave the due date unset. Do not invent deadlines.
If an action item has sub-steps ("draft the deck, get Sam to review, then send it"), do not cram them into the title. Create the parent task first, then call Create Checklist Item on that task for each sub-step in order.
Quality bar: titles should be specific and verb-first. The body should always include enough context that I know which meeting it came from without opening Granola. When in doubt about ownership, skip the item rather than file a task that is not mine.
What it does
- Watches Granola for new meeting notes and triggers the moment one shows up.
- Reads the summary, attendees, and transcript to find action items that are clearly yours or unowned and obviously yours to handle.
- Creates a clean Microsoft To Do task for each one with a one-line title, the meeting context, and the exact line from the note that justified it.
- Adds a due date when the note mentions one, and breaks multi-step items into checklist subtasks instead of cramming them into the title.
- Skips quietly when a meeting has no real action items, so casual calls never leave phantom tasks behind.
What you’ll need
- A Granola account on the Business or Enterprise plan with personal API keys enabled.
- A Microsoft account with Microsoft To Do, signed in with permission to read and write tasks.
- Optional: a Microsoft To Do list named "Meetings" if you want meeting follow-ups kept separate from your default list.
How to customize it
- Change which list tasks land in, for example a dedicated "Meetings" list or your default Tasks list.
- Tighten or loosen ownership rules, like accepting items addressed to your team or only items where you are named directly.
- Tune the default due date when the note does not specify one, for example end of week instead of leaving it unset.
Use cases
- Meeting Workflows
