Meeting Recap Emails: Claude + Make

A nonprofit board meets monthly, and the secretary is supposed to send a recap afterward. By the time the meeting ends it is late, everyone is tired, and the recap that would keep the board aligned slips a week, then never goes at all. The transcript exists; the write-up is the part that does not happen.

This build writes it. Drop the transcript into a Drive folder, and Make reads it, hands it to Claude for a clean recap with the decisions made and the action items assigned, and emails it out. The meeting documents itself while everyone is still saying goodbye.

We wire it in Make, the first build in our meeting notes set. Most video tools (Meet, Zoom, Otter) can save a transcript to Drive; once it is there, this takes over. Claude does the summarizing, which is exactly what it is best at.

What does this workflow actually do?

In one line: a transcript becomes a recap email. Make watches a Drive folder. When a transcript lands, it reads the text, hands it to Claude for a structured recap, and emails the result. The raw transcript stays in Drive; the inbox gets the clean version people will actually read.

A few real cases, none of them the usual ones:

• The nonprofit board secretary above, sending the recap before everyone has left the call.
• A startup founder emailing an investor-update recap right after each call.
• A wedding planner sending the couple a recap of every vendor meeting.
• A school principal recapping staff meetings to the teachers who could not attend.

Holding the meeting is the work. Writing it up so the decisions stick is the chore that decides whether the meeting mattered. That write-up is exactly what Claude is good at.

Why use Make if Claude can already summarize?

Fair question. Claude is excellent at turning a transcript into a clean recap. It is not built to watch a Drive folder, read the file, and email the result on its own. That is plumbing, and Make does plumbing.

Make handles the no-judgment steps: noticing the transcript, reading it, sending the email, running unattended. Claude handles the one step that needs language, the recap. Make is the messenger; Claude is the writer. Together a finished recap goes out minutes after the meeting, instead of next week or never.

What do you need before you start?

• A Make account. The free 1,000 operations a month covers a busy meeting schedule.
• A Claude API key from the Claude console, not the chat app. New to Claude? See how to use Claude.
• A Google account with a Drive folder where your transcripts land.
• A Gmail account to send the recap from (Outlook works with its own module).

Two Make words, once. A scenario is one automation, the whole transcript-to-email chain. A module is one box. Four boxes here, because reading the document is its own step.

How does the workflow work, step by step?

Four modules, left to right:

Module	App	What it does
1. Trigger	Google Drive	Fires when a transcript lands in the folder
2. Read	Google Docs	Pulls the transcript text out
3. Brain	Claude	Writes the recap, decisions, and action items
4. Output	Gmail	Emails the recap

Step 1: Watch a transcripts folder

Create a scenario and add Google Drive, Watch Files in a Folder, connect your account, and pick the folder your meeting transcripts save into. This trigger fires on each new transcript.

Step 2: Read the transcript

Add Google Docs, Get Content of a Document and map the file from Step 1. This pulls the words out so Claude has the meeting to work from. For Google Docs transcripts this is instant.

Step 3: Let Claude write the recap

Add a Claude module (Anthropic), Create a Prompt, paste your key, pick Sonnet. Give it a clear shape:

Write a meeting recap from this transcript.
Transcript: {{content from Step 2}}

Give: a 3-sentence summary, then "Decisions:" as a short list, then
"Action items:" as a list of owner and task. Keep names and facts
exact. Do not invent anything not in the transcript.

The decisions-and-action-items shape is what makes the recap useful instead of just a summary, and the no-invention rule keeps it true to the meeting.

Step 4: Email the recap

Add Gmail, Send an email, set the recipients (a team alias works well), map the recap into the body and a clear subject with the meeting name and date. Now the recap goes out on its own. Want a human check first? Use Create a draft instead of Send.

How do you run it and check the result?

Click Run once after dropping a test transcript in the folder. When I tested this, the recap came back well-structured, and the rule that mattered was telling Claude to keep names and facts exact and invent nothing, so the action items matched what was actually said. Tune the prompt, then turn the scenario on so meetings recap themselves.

After that, the recap stops being the thing nobody does. Every meeting produces its own clean summary minutes after it ends, and the decisions made in the room actually reach the people who need them.

What does this cost to run?

Piece	Free tier	If you outgrow it
Make	1,000 operations/month free	Core plan from about $9/month
Claude API	Pay per use	A recap on Sonnet costs a fraction of a cent
Google Drive + Docs	Free	Free with your account
Gmail	Free	Free

Each meeting is four Make operations and a sliver of Claude. A full calendar sits inside the free plan. For tiers, see our Make beginner’s guide.

What can go wrong, and how do you avoid it?

• It adds things that were not said. Keep the no-invention rule in the prompt; the recap must match the transcript.
• It sends before you check. Use Create a draft instead of Send if you want a human glance first, especially for sensitive meetings.
• No transcript to read. Make sure your meeting tool actually saves a transcript to the folder; without one there is nothing to summarize.
• Long meetings hit limits. Very long transcripts may need trimming or summarizing in sections.

Want more of this pattern? Our Make AI scenarios roundup has the next ideas.

How do you build this in Zapier or n8n instead?

The four jobs do not change, only the names do.

Job	Make	Zapier	n8n
Catch a transcript	Watch Files in a Folder	New File in Folder trigger	Google Drive Trigger node
Read it	Get Content of a Document	Get Document action	Google Docs node
Write the recap	Claude module	Claude (Anthropic) action	Anthropic node
Email it	Send an email	Gmail Send Email	Gmail node

Make and Zapier are the gentlest for a first build. Zapier vs Make vs n8n compares all three.

Common questions

Where does the transcript come from?

From your meeting tool. Google Meet, Zoom, and Otter can save transcripts to Drive. Once a transcript is in the folder, this build takes over.

Can it email the whole team?

Yes. Send to a team alias or a list. To control who gets it, set the recipients in the Gmail step.

What if I want to review before it sends?

Use Create a draft instead of Send. The recap waits in your drafts for a glance, which is wise for sensitive meetings.

Does it keep the full transcript?

Yes. The transcript stays in Drive untouched; the email is the clean recap built from it.

Is the Claude chat app the same as the API?

Same models, different door. Make talks to the API, so you need a key from the console.

Sources and docs

• Creating a scenario (Make Help)
• Claude API overview (Anthropic)
• Google Docs basics (Google)
• Claude on Make (integrations)
• Meeting minutes — Grokipedia

Last reviewed: May 2026. Make, Claude, and Google update their interfaces; check the official pages for exact button names.

You may also like

• AI Automation for Beginners (the hub)
• Summarize new documents with Claude + Make
• Log sales-call notes to your CRM with Claude
• Make.com Complete Beginner’s Guide
• How to use Claude AI
• Zapier vs Make vs n8n: which to start with
• The AI Tools Directory