Automated Meeting Intelligence with Claude Code and n8n

What Is Automated Meeting Intelligence with Claude Code and n8n

Automated meeting intelligence with Claude Code and n8n is a pipeline that transforms every meeting from a forgettable conversation into a structured knowledge asset. When a Google Calendar event with a Zoom or Google Meet link ends, n8n triggers the post-meeting workflow. It downloads the transcript from the provider's cloud recording, sends the full transcript to Claude Code via the n8n MCP server for multi-layered analysis, stores action items and decisions in Mem0 for persistent memory across meetings, creates a structured Notion page with all meeting outputs, and sends Slack direct messages to each action item owner with their assignments. The pipeline eliminates manual note-taking, ensures decisions are documented, action items are tracked, and meeting context accumulates over time rather than resetting with every calendar invite.

[TOOL: n8n MCP Server] The n8n-mcp npm package exposes seven workflow management tools to Claude Code. The execute_workflow tool lets Claude trigger the post-meeting pipeline. Configure with N8N_API_URL and N8N_API_KEY environment variables.

[ TOOL: Claude Code CLI ] Claude Code operates in two phases. MCP mode provides live read/write access to n8n workflows. Reasoning mode generates the structured meeting summary. Claude returns an executive brief, decisions list, action items with owners, unresolved questions, and topic timestamps.

[ TOOL: Google Calendar API ] Google Calendar trigger queries events ending in the last 2 hours with conference link properties. Uses OAuth 2.0 with calendar.events.readonly scope.

[ TOOL: Zoom API ] Zoom API downloads cloud recording transcripts from completed meetings. Uses a Server-to-Server OAuth app with meeting_recording:read:admin and past_meeting:read:admin scopes.

[ TOOL: Google Meet API ] Google Meet API exports transcripts for Workspace accounts with recording enabled. Provides the transcript as a structured text output.

[ TOOL: Mem0 ] Mem0 stores action items and decisions as memory entries associated with attendee user IDs. Provides persistent context across meetings for coherent long-term recall.

[ TOOL: Notion API ] Notion creates a page in the Meetings database with all structured fields, the full transcript as a child block, and links to the calendar event and recording.

[ TOOL: Slack ] Slack sends direct messages to each action item owner with their specific action, deadline, and a link to the Notion meeting page.

[ STAT ] Professionals spend 31 hours per month in meetings, with 30 percent of meeting time considered unproductive due to poor follow-through. Source, Atlassian Workforce Survey, 2024.

[ STAT ] n8n-mcp npm package has 22K GitHub stars and supports all n8n workflow operations via MCP protocol. Source, czlonkowski, 2026.

[ STAT ] 47 percent of employees say lack of meeting documentation causes them to redo work or miss deadlines. Source, Doodle State of Meetings Report, 2024.

How the Meeting Intelligence Workflow Works Step by Step

1. The Google Calendar trigger node runs every 15 minutes, querying events that ended in the last 2 hours. Filters for events with conference links containing zoom.us or meet.google.com. Passes the event ID, title, start/end time, attendee list, and conference link to the pipeline.

2. An IF node checks the conference link domain. If it contains zoom.us, route to the Zoom API node. If it contains meet.google.com, route to the Google Meet API node. Each node downloads the transcript text.

3. An HTTP Request node sends the full transcript, event title, attendee list, and meeting duration to Claude Code via the n8n MCP server. Claude returns a structured JSON object containing: one-paragraph executive brief, numbered decisions list, action items with owner and deadline, unresolved questions, key topics with timestamp markers.

4. The Mem0 node iterates through the action items and decisions from Claude's output. Stores each as a memory entry associated with the relevant attendee's user ID. Future meeting summaries query Mem0 for relevant past context before generating the summary.

5. The Notion node creates a new page in the Meetings database. Sets page properties: meeting title, date, duration, attendee count, and decision count. Appends child blocks: executive brief callout, decisions toggle, action items checklist, and full transcript as a code block.

6. A Loop node iterates through each action item from Claude's output. For each item, the Slack node sends a direct message to the assigned owner. The message includes the action description, deadline, and a link to the Notion meeting page.

[ STAT ] Claude Code MCP mode provides live read/write API access to n8n workflows for creating, updating, and executing automation pipelines. Source, Alex P., AI Systems Lab, Medium, 2026.

Three Critical GOTCHAs You Must Know Before Running This Workflow

GOTCHA 1: Zoom transcript availability is not instant. Cloud recording processing takes 10-30 minutes after a meeting ends depending on meeting duration. Add a Wait node with a 10-minute initial delay and a retry loop with exponential backoff up to 3 attempts.

GOTCHA 2: Google Meet transcripts are only available for Google Workspace accounts with recording enabled. Standard free Google accounts do not produce meeting transcripts. Verify Workspace account status before building the Google Meet branch.

GOTCHA 3: Mem0 user IDs must match attendee email addresses from Google Calendar for context linking to work. If the Mem0 user ID format differs from email addresses, context retrieval returns empty results. Normalize the user ID format across both systems.

Meeting Intelligence ROI and Time Savings

1. Note-taking time eliminated: average 15 minutes of manual notes per 60-minute meeting recovered for active participation. 2. Action item completion rate increases by 35 percent when owners receive automated Slack DMs with their specific assignments. 3. Knowledge retention improves as Mem0 carries context across recurring meetings, reducing repeated discussions by an estimated 20 percent. 4. Asynchronous access to meeting intelligence: non-attendees consume the full 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 previously spent on notes and follow-up tracking.

Setup Requirements and Common Pitfalls

1. (significant risk) Zoom cloud recordings may fail to process for meetings under 60 seconds or over 4 hours. Add error handling that sends a Slack alert if transcript download fails after 3 retries. 2. (moderate risk) Mem0 memory accumulates without a pruning strategy. Set a 90-day retention window to prevent irrelevant context from appearing in summaries. 3. (moderate risk) Notion API rate limits at 3 requests per second per integration. Bulk backfill of past meetings must be throttled with a Wait node. 4. (minor) Claude Code cannot set Notion or Mem0 API credentials — all tokens configured in n8n UI before first run.

Q: Can this workflow process meetings held in Microsoft Teams? A: Yes. Add an additional IF branch for teams.microsoft.com links and use the Microsoft Graph API to download Teams meeting transcripts.

Q: How does Mem0 improve meeting summaries over time? A: Mem0 stores decisions and action items from past meetings. When Claude generates a summary for a recurring meeting, it queries Mem0 for relevant context and includes references to past decisions, creating continuity across meeting series.

Q: What happens if a meeting has no transcript available? A: The workflow sends a Slack alert with the meeting title and a message that no transcript was found. It creates a basic Notion page with just the calendar metadata and a note that the transcript was unavailable.

Q: Does Claude Code generate the entire meeting intelligence workflow automatically? A: Yes. Noah Albert of RoboRhythms documents that Claude Code built the complete workflow including all node configurations, API integrations, and error handling by generating n8n workflow JSON.