CASE STUDY
How a weekly team meeting became a structured decision record in under 2 minutes,without anyone writing notes
Weekly meetings covered two markets and multiple campaigns,but the only record of what happened was whatever each person happened to write down for themselves. No shared decisions, no owner-tagged tasks, no searchable history. This system fixed that at the transcript level, before anyone opened a task manager.
THE PROBLEM
Good decisions were made in the meeting. By Friday, no one could remember who owned what.
The team had a weekly sync covering campaign performance, budget decisions, and upcoming action items across SG and MY. The call would end with 4-6 things agreed upon,but the only record was whatever notes each person happened to type for themselves. No shared log, no structured owner assignments, nothing searchable. Tasks fell through. The same conversation happened again the following week.
"The problem wasn't that people weren't paying attention. It was that 'write the meeting notes and create the tasks' was a manual step that happened after the call,when everyone was already moving on to the next thing. Automating that step meant the record existed before anyone closed their laptop."
THE PIPELINE
From raw transcript to structured record,fully automated
System 2 (n8n stack): transcript file → n8n webhook → GPT-4o → Notion page
HOW IT WORKS
Six steps, zero manual write-ups
Transcript is pasted into the PowerShell script
No upload UI, no app to open. The transcript text goes in as a parameter. Works with any transcript format,Zoom, Fireflies, manual copy-paste.
Claude AI extracts the structured meeting record
Prompt extracts: meeting summary, decisions made, action items with inferred owners and due dates, and open questions. Each action item is scored for priority based on context, not just keywords.
Owner inference from context
Claude assigns owners based on who was mentioned in relation to the task, not just who was speaking. If 'Jowel will update the brief by Thursday' is in the transcript, Jowel gets that task,no manual assignment.
Individual ClickUp tasks created for Jowel's items only
Only tasks where Jowel is the inferred owner get created as ClickUp tasks. Other team members' tasks appear in the meeting note for visibility but don't clutter Jowel's task inbox.
Full meeting note written to ClickUp as a searchable record
The complete structured output,summary, decisions, all action items, open questions,goes into ClickUp as a doc. Every meeting is findable by date, campaign, or keyword.
System 2: same extraction pattern on n8n + Notion
Rebuilt the same extraction logic on a second stack (n8n + GPT-4o + Notion API) for teams that live in Notion instead of ClickUp. Same output structure, different toolchain,proves the system isn't locked to one stack.
EVIDENCE
Inside both stacks
System 1,ClickUp meeting note output with structured action items
System 2,n8n workflow canvas handling transcript extraction
System 2,Notion meeting page output from the n8n pipeline
RESULTS
What changed after deployment
→ Meeting record exists in under 2 minutes
Before the next meeting's agenda is open, the previous meeting's decisions and tasks are already in ClickUp.
→ 30+ tasks auto-created across 11 meetings
Tasks that would have been manually created (or forgotten) are now auto-generated with the right owner and due date inferred from transcript context.
→ Zero duplicate conversations
Every decision is searchable. When a question comes up the following week, the answer is already in the meeting record from the week before.
→ Two stacks, one extraction pattern
Proving the system works on both PowerShell+Claude and n8n+GPT+Notion shows it's adaptable to whatever tools a client already uses.
KEY ENGINEERING DECISIONS
Why owner-only task creation matters
The first version created a task in ClickUp for every action item mentioned in the meeting, regardless of who owned it. This created noise,Jowel's ClickUp became a mirror of everyone else's workload, not just his own. The fix was to keep the full record in the meeting note (so nothing is hidden) but only auto-create tasks for Jowel's items.
"A task manager that has everyone's work in it isn't useful for managing your own work. The system needed to be opinionated about what goes into ClickUp as a task vs. what stays as a record. The meeting note holds everything,the task list holds only what you're accountable for."
Building on two separate stacks was also intentional. A client who lives in Notion can't be told to switch to ClickUp for this system to work. By proving the extraction pattern works on both PowerShell+Claude and n8n+GPT+Notion, the system becomes tool-agnostic,which is what makes it sellable to teams regardless of their existing stack.
SIMILAR USE CASES
Where this system applies
Any recurring meeting where decisions get made and tasks need to be tracked,client calls, team standups, investor updates, sales debrief calls. The extraction prompt adapts to the meeting type; the task-creation and record-keeping logic stays the same.