Build an AI Meeting Summarizer Workflow: Save Hours Every Week

The average knowledge worker sits in 10+ hours of meetings per week and leaves most of them with vague notes and no clear action items. An AI meeting summarizer workflow changes that — automatically converting raw transcripts or rough notes into structured summaries, decision logs, and follow-up tasks within minutes of a call ending.

Step 1: Get Your Transcript

You need a raw transcript to work with. There are three common ways to get one:

Option A — Fireflies.ai or Otter.ai: These tools auto-join your Zoom, Google Meet, or Teams calls and produce a timestamped transcript. Free tiers cover most individual use cases. Export the transcript as plain text.

Option B — Zoom built-in transcription: Zoom Pro and above includes AI-generated transcripts. Go to the recording page, download the VTT file, and strip the timestamps using a simple script or find-and-replace.

Option C — Manual notes: If you do not record calls, even rough bullet-point notes work. The AI will still produce something far more useful than what you wrote in the moment.

Step 2: The Core Summarizer Prompt

Once you have a transcript, paste it into Claude or ChatGPT with this prompt:

You are an expert at extracting signal from meeting transcripts.
Read the transcript below and produce:

1. **TL;DR** (2–3 sentences): What was this meeting about and what was decided?
2. **Key Decisions** (bullet list): Only include firm decisions, not discussion points.
3. **Action Items** (table): | Owner | Task | Due Date |
4. **Open Questions** (bullet list): Unresolved issues that need follow-up.
5. **Next Meeting** (1 line): Recommended agenda for the follow-up, if applicable.

Be specific. Use the names from the transcript for owners.
Do not include filler or restate the discussion — only outcomes.

Transcript:
[paste transcript here]

This prompt reliably produces a summary you can send directly to attendees without editing. The key is the instruction "do not restate the discussion" — without it, AI models tend to narrate what was said rather than extract what matters.

Step 3: Automate the Routing with Make.com

Running the prompt manually works, but the real leverage comes from automating the whole pipeline. With Make.com, you can build a workflow that runs end-to-end without you touching anything:

Here is the flow:

Trigger: New recording in Google Drive folder (or Fireflies webhook)
  ↓
Step 1: Download transcript file
  ↓
Step 2: HTTP module → OpenAI or Claude API with the summarizer prompt
  ↓
Step 3: Parse the structured output (TL;DR, decisions, action items)
  ↓
Step 4a: Send summary email to meeting attendees via Gmail
Step 4b: Create tasks in your project tracker (Notion, Asana, ClickUp)
Step 4c: Log the summary to a Notion database (meeting archive)

Setting this up in Make.com takes about 45 minutes the first time. Once it is running, every recorded meeting automatically produces a summary email and tasks — no manual work required. Make.com has pre-built modules for Google Drive, Gmail, Notion, Asana, OpenAI, and dozens of other tools, so most of this is drag-and-drop.

Step 4: Specialized Prompts for Different Meeting Types

The generic summarizer works well, but you can get better results by tailoring the prompt to the meeting type:

For client calls: Add "Extract any commitments made by our team and flag any scope changes or new requests from the client." This keeps your CRM notes accurate and surfaces scope creep early.

For 1:1s: Add "Identify any blockers the person mentioned, career development topics raised, and any feedback given or received." This makes 1:1 notes actually useful for performance reviews.

For brainstorming sessions: Add "List all distinct ideas mentioned, grouped by theme, regardless of whether they were endorsed or rejected." Brainstorms lose 60% of their ideas by the end of the day without this.

Step 5: Build a Searchable Meeting Archive

The compounding value of this workflow comes over time. If every meeting summary lands in a structured Notion database, you can search across months of meetings to answer questions like "what did we decide about the pricing model in Q1?" or "who owns the API integration task from the March kickoff?"

Set up your Notion database with these fields: Meeting Name, Date, Attendees (multi-select), Decisions (text), Action Items (linked to your tasks database), and Status (Open / Archived). Use the Make.com automation to populate these fields automatically from the AI output. Within a month, you will have a meeting archive that actually earns its keep.

Get AI workflows in your inbox

One weekly email with real-world AI workflows, prompts that actually work, and tool recommendations. No fluff.