Turn meeting notes into action items
Extract decisions and actions with owners, confirm them, and create the tasks.
Turning meeting notes into action items is the step everyone skips. The meeting ends, the transcript exists, and three days later nobody remembers who owned what. This workflow reads the transcript or raw notes, extracts decisions and actions with owners and deadlines, confirms them with the people named, and creates the tasks where your team works.
What does this workflow do?
After a meeting, the agent takes the transcript from Fireflies or Granola (or notes you paste in) and produces a structured summary: decisions made, actions agreed, owner and deadline per action, and open questions that never got resolved.
Then it closes the loop. Each owner gets a short Slack confirmation: "From today's planning meeting: you own the pricing page update, due Friday. Correct?" Confirmed actions become Linear issues or Notion tasks. Corrections happen in one tap, before a wrong task exists anywhere.
How does it work?
- The workflow sweeps for new transcripts. On an hourly schedule it picks up meetings Fireflies or Granola finished since the last run, or you paste notes and run it on demand.
- The agent extracts the structure. Decisions, action items, owners, deadlines and open questions. It knows who's who, so "Sara takes the follow-up" resolves to the right Sara.
- Owners confirm in Slack. Each named person gets their items to confirm or correct. Unclaimed actions go back to the meeting organizer.
- Tasks get created. Confirmed items land in Linear or Notion with the meeting linked. The summary posts to the meeting channel and archives.
- Open questions get chased. Questions the meeting left unresolved become information requests to whoever can answer, so "we never decided on X" surfaces before the next meeting.
Why do owners need to confirm?
An unconfirmed action item is a suggestion. Meeting bots that post summaries to a channel move the problem from "nobody wrote it down" to "nobody read it." The confirmation step costs each person one tap and produces the thing that was missing: acknowledged ownership.
The workflow also learns your team's conventions: which project each meeting's tasks belong to, who "the design team" means, what your default deadline is when nobody says one. Decisions extracted from meetings persist in the knowledge base, so "when did we decide this?" has a source.
Works with
Fireflies, Granola, Slack, Linear, Notion, Google Docs. Runs on an hourly schedule against new transcripts, or on demand with pasted notes.
Frequently asked questions
Does it work without a meeting recorder?
Yes. Paste raw notes or a Google Doc and run it on demand. With Fireflies or Granola connected, an hourly scheduled sweep picks up each recorded meeting shortly after it ends.
What if the transcript is ambiguous about who owns something?
The agent asks rather than guesses. Ambiguous items go to the meeting organizer with a one-tap prompt to assign an owner.
Where do the tasks go?
Linear or Notion, your choice per meeting type or per team. Each task links back to the meeting summary, and the workflow learns which project tasks from each recurring meeting belong to.
Do people get spammed after every meeting?
No. Each person gets one message listing only their items. Meetings with no actions produce no messages, and you can mute confirmations for standups or other meeting types.
What happens to decisions that aren't action items?
They're kept. Decisions get recorded in the knowledge base with the meeting as source, so later questions like "why did we pick this vendor?" return an answer with a link.