Meeting Intelligence with Claude Code Transcript Analysis

This workflow triggers on Google Calendar events that include a Zoom or Google Meet link. When the event status changes to completed, n8n begins the post-meeting pipeline. It retrieves the meeting transcript from Zoom's cloud recording API or Google Meet's transcript export. The raw transcript text is sent to Claude Code via the n8n MCP server for multi-layered analysis — Claude generates a structured meeting summary with key decisions, action items with assigned owners, unresolved questions, and a one-paragraph executive brief. The action items and decisions are stored in Mem0, a memory layer that maintains persistent context across meetings, so Claude can reference past discussions in future meeting summaries. A Notion database page is created under the Meetings database with all structured fields, the full transcript as a child block, and links to the calendar event and recording. The assigned team members receive a Slack direct message with their action items. [ STAT ] Professionals spend an average of 31 hours per month in meetings, with 30 percent of meeting time considered unproductive due to poor follow-through — Source, Atlassian Workforce Survey, 2024.

BUSINESS PROBLEM

Meeting documentation is the most commonly neglected knowledge management task. Attendees take incomplete notes, action items go unassigned, and decisions made in meetings are forgotten within days. The problem compounds across recurring meetings — what was decided in the last sprint retro is lost by the next planning session. [ STAT ] 47 percent of employees say the lack of meeting documentation causes them to redo work or miss deadlines — Source, Doodle State of Meetings Report, 2024. Manual meeting note-taking also reduces active participation — attendees who take notes recall 20 percent less discussion content than passive listeners. This workflow eliminates note-taking entirely by capturing, analyzing, and distributing meeting intelligence automatically.

WHO BENEFITS

FOR engineering team leads SITUATION: runs 15-20 meetings per week across standups, sprint planning, and one-on-ones PAYOFF: every decision and action item is captured consistently without any manual effort. FOR product managers SITUATION: synthesizes feedback from customer calls, stakeholder reviews, and internal planning sessions PAYOFF: Mem0 memory maintains context across all product-related meetings for coherent long-term recall. FOR operations directors SITUATION: needs to audit decisions made across multiple department meetings PAYOFF: Notion database provides a searchable, structured archive of all meeting outputs with cross-references.

HOW IT WORKS

1. Google Calendar trigger runs every 15 minutes, querying events that ended in the last 2 hours with conference links. Filtered by calendar ID and event status = completed.

2. IF node splits by provider: Zoom events route to Zoom API node, Google Meet events route to Google Meet API node. Both nodes download the transcript text.

3. Claude Code MCP node receives the full transcript, event title, attendee list, and duration. Returns structured JSON: one-paragraph executive brief, numbered decisions list, action items with owner/ deadline, unresolved questions, key topics with timestamps.

4. Mem0 node stores action items and decisions as memory entries associated with each attendee's user ID. Future meeting summaries will include relevant past context from Mem0.

5. Notion node creates a new page in the Meetings database. Page properties include meeting title, date, duration, attendee count, and decision count. Page body includes Claude's executive brief, decisions, action items, and the full transcript as a toggle block.

6. Slack node iterates through action items and sends a direct message to each assigned owner with their specific action, deadline, and a link to the Notion meeting page.

TOOL INTEGRATION

Google Calendar API uses OAuth 2.0 with the calendar.events.readonly scope. GOTCHA: The events.list query using timeMin and timeMax must use RFC 3339 timestamp format with timezone offset. Zoom API requires a Server-to-Server OAuth app with the meeting_recording:read:admin and past_meeting:read:admin scopes. GOTCHA: Zoom cloud recordings take 5-30 minutes to process after a meeting ends — add a Wait node with a 10-minute delay before requesting the transcript to avoid empty responses. Mem0 integration uses the Mem0 REST API with an API key for memory storage. GOTCHA: Mem0 user IDs must match the email addresses from the Google Calendar attendee list for context linking to work correctly. Notion API requires an integration token from Notion Integrations dashboard with insert and update capabilities on the target database. GOTCHA: Notion database property names must exactly match the field map in the Notion node — a misspelled property name causes the page to be created without that field. Claude Code MCP receives the transcript. GOTCHA: Claude Code cannot set Notion or Mem0 API credentials — all tokens must be configured in n8n UI manually before the workflow runs.

ROI METRICS

1. Note-taking time eliminated: average 15 minutes of note-taking per 60-minute meeting recovered. 2. Action item completion rate: teams with automated action item tracking show 35 percent higher task completion within deadlines. 3. Knowledge retention: Mem0-powered context carryover reduces repeated discussions by an estimated 20 percent across recurring meetings. 4. Asynchronous access: Notion database gives non-attendees complete meeting context in 2-3 minutes of reading instead of scheduling a 30-minute debrief. 5. Monthly hours saved: 6-8 hours per knowledge worker per month previously spent on notes and follow-ups.

CAVEATS

1. (significant risk) Zoom transcript availability is not instant — processing can take 10-30 minutes for cloud recordings. The 10-minute Wait node may not be sufficient for longer meetings. Implement a retry loop with exponential backoff. 2. (moderate risk) Google Meet transcripts are only available for Workspace accounts with recording enabled. Standard Google accounts do not produce meeting transcripts. 3. (moderate risk) Mem0 memory accumulates over time — without a pruning strategy, context retrieval may return irrelevant past entries. Set a 90-day memory retention window. 4. (minor) Notion API rate limits: 3 requests per second per integration. Bulk backfill of past meetings must be throttled.