Overview
Meeting transcripts pile up in Fathom or Otter, and action items get lost. This n8n workflow watches a Drive folder, extracts action items with Claude (owner, description, deadline, context), and creates Linear issues in the right team with a Notion page linked for full context.
How it works
- Google Drive trigger on new file in /transcripts.
- Claude extracts action items as structured JSON.
- For each item: create Linear issue with owner, due date, and a link to the source transcript in Notion.
- Post a summary to the meeting channel.
Benefits
- No action item lost between meeting and standup.
- Owner assignment done in the extraction step, not later in triage.
- Every issue links to the full transcript for context.
Use cases
- Weekly leadership meetings.
- Customer discovery calls that generate follow-ups.
- Cross-functional standups.
Step-by-step guide
Step 1: Set the folder + naming convention
/transcripts/{date}-{meeting-name}.txt. Include participants in the filename or first line.
Step 2: Extraction prompt
System: 'Extract action items as JSON: {owner, description, due_date?, priority?, context}. Owner must be one of {team members list}. Deadline is inferred from phrases like next week, before shipping.'
Step 3: Linear creation
Map owner name → Linear user ID via a static mapping. Team based on meeting name. Add Notion link in the description.
Step 4: Notion page for full transcript
Create a page with the full text; link its URL from every issue.
Step 5: Slack summary
'{Meeting name} — 6 action items created. See Linear board {link}.'
Example
Item: {owner:'Sam', description:'Draft SOC2 policy doc', due:'2026-06-15', context:'Enterprise deal requires it by procurement review'}.