Turn Granola action items into Google Tasks

By General Input

When a new Granola note lands, an agent picks the action items you own, infers due dates, and files them into your Google Tasks Follow-ups list.

Integrations

  • Granola
  • Google Tasks

Type

Agentic Task

Categories

  • Personal Productivity
  • Operations

Build me an agent workflow that turns my Granola meeting notes into Google Tasks so I never lose a follow-up again.

Trigger: poll Granola for new notes. Fire once per newly created Granola meeting note.

When the trigger fires, the agent should:

1) Call Granola Get Note with the new note's id and include the transcript so you have the full summary, attendees, calendar event, and transcript text. Capture the meeting title, meeting date/time, attendees, the note's web link, and the summary markdown.

2) Identify who "me" is. Use the connected Granola account's identity (or fall back to a configurable display name the user will set when they install this). Treat the user as "me" when matching attendees and action item owners.

3) From the summary and transcript, extract every action item. For each one, decide who owns it. Only keep action items where the owner is me, where the note explicitly assigns it to me, or where I clearly committed to it in the transcript ("I'll send that", "I'll set that up", etc.). Skip every action item owned by another attendee.

4) For each kept action item, infer a due date from natural language phrases in the note. Examples: "by Friday" -> the next Friday after the meeting, "next week" -> the following Monday, "by end of month" -> the last day of the month, "tomorrow" -> meeting date + 1 day. If there is no due date language, leave the due date unset rather than guessing. Use the meeting date as the anchor for relative phrases, not today's date.

5) Before creating tasks, call Google Tasks List Task Lists to find a list named "Follow-ups" (case-insensitive). If it doesn't exist, create it with Create Task List. Then call List Tasks on that list with showCompleted=false to get the open tasks already on it, so you can dedupe.

6) For each kept action item, dedupe against the open Follow-ups tasks: if there's already an open task whose notes reference the same Granola note link and whose title describes the same action, skip it. Otherwise, call Google Tasks Create Task on the Follow-ups list with:

- title: the concrete action in imperative voice ("Send the pricing deck to Acme", not "sending the pricing deck").

- due: the inferred due date in RFC 3339 (the time portion is ignored by Google Tasks, that's fine).

- notes: a short block that contains the meeting title, the meeting date, the attendee who raised the action item (or "self-committed" if it was me), the verbatim quote from the note or transcript, and the Granola note link so I can reopen the source context in one click.

- status: needsAction.

7) If the meeting had zero action items that belong to me, do nothing. Don't create a placeholder task and don't post anywhere. A clean exit is the right outcome.

Keep the title under 1024 characters and the notes under 8192 characters (Google Tasks limits). The Follow-ups list name should be configurable at install time. Only Granola and Google Tasks are needed, no third tool.

Related prompts

Explore more prompts
Run every client's delivery from one board, not ten task listsEvery Google Tasks list on one board, grouped by due dateTurn Granola interviews into a themed customer research repositoryPre-call prep board for your next three days of meetingsA Friday weekly review desk built on your Google TasksSpot the deals that went quiet before your pipeline reviewTurn Granola meeting notes into Bigin calls, tasks, and stage updatesTurn today's Granola meeting notes into TickTick tasksPublish today's meeting notes to Confluence every eveningClaude-powered Granola to Linear action items with a Slack recap