Recap to Slack: Claude + Make

A remote team spans three time zones, so half of them are asleep during any given meeting. The recap that would keep the sleepers in the loop depends on someone writing it up after a long call, which is exactly when nobody wants to. So the async half drifts out of sync, one missed meeting at a time.

This build keeps everyone current. Drop the transcript into a Drive folder, and Claude writes a clean recap, and Make posts it to the team’s Slack channel. The people who were asleep wake up to the decisions and the action items, without anyone staying late to type them.

We wire it in Make, the last build in our meeting notes set. Same recap shape as the email and Notion versions, pointed at Slack, because async teams live in their channels.

What does this workflow actually do?

In one line: a transcript becomes a Slack post. Make watches a Drive folder, reads the transcript, has Claude write a recap, and posts it to a Slack channel. The meeting reaches the whole team, including whoever could not attend, in the place they already check.

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

• The remote team above, the sleeping time zone waking up to the recap.
• A volunteer organization recapping calls to its Slack so busy members stay in the loop.
• A dev team posting sprint-planning recaps to the engineering channel.
• A sales team posting deal-review recaps to a shared channel.

The meeting happens once; the people who missed it are the ones who need the recap most. Getting it to them reliably is the chore that slips. An automation never forgets.

Why use Make if Claude can already summarize?

Reasonable question. Claude writes the recap. It is not built to watch a Drive folder, read the transcript, and post to Slack on its own. That is plumbing, and Make does plumbing.

Make handles the no-judgment steps: catching the transcript, reading it, posting to the channel, running unattended. Claude handles the one step that needs language, the recap. Make is the announcer; Claude is the writer. Together the team gets the recap minutes after the meeting, no matter who was awake for it.

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 console, not the chat app. See how to use Claude.
• A Google account with a Drive folder of transcripts.
• A Slack workspace and a channel to post into, with permission for the connection to post.

Two Make words. A scenario is the whole transcript-to-Slack automation. A module is one box. Four boxes, 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 a clean, channel-friendly recap
4. Output	Slack	Posts the recap to the channel

Step 1: Watch a transcripts folder

Create a scenario and add Google Drive, Watch Files in a Folder, connect your account, and pick the transcripts folder. 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, which pulls the text out for Claude.

Step 3: Let Claude write the recap

Add a Claude module, Create a Prompt, paste your key, pick Sonnet. Keep it short for a channel:

Write a short Slack recap of this meeting.
Transcript: {{content from Step 2}}

A 2-sentence summary, then *Decisions* and *Action items* as short
bulleted lists with owners. Keep it tight for a channel. Facts
exact, invent nothing.

Slack rewards brevity, so ask for a tight recap, not a full memo; people skim channels.

Step 4: Post it to Slack

Add Slack, Send a Message, connect Slack, pick the channel, and map Claude’s recap into the message. Now every meeting posts its own recap where the team already is.

How do you run it and check the result?

Click Run once on a test transcript. When I tested this, the recap posted to Slack cleanly, and the tweak that mattered was telling Claude to keep it tight, because a wall of text dies in a channel. Tune the prompt, then turn the scenario on so meetings recap themselves into Slack.

After that, the async half of the team stops drifting. Every meeting lands in the channel as a short, skimmable recap, and being asleep for it stops meaning being out of the loop.

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
Slack	Free plan works	Paid from about $7/user/month

Each meeting is four Make operations and a sliver of Claude. A full calendar sits inside the free plan. More on tiers in our Make guide.

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

• The recap is too long for a channel. Ask Claude to keep it tight; channels reward brevity.
• It posts to the wrong channel. Set the channel carefully in the Slack step.
• It invents content. Keep the no-invention rule so the recap matches the meeting.
• Slack rejects the post. Check the connection has permission to post in that channel.

The same recap-to-channel shape runs many jobs. See Make AI scenarios.

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
Post to Slack	Send a Message	Slack Send Channel Message	Slack node

Make and Zapier are easiest to start. Zapier vs Make vs n8n compares all three.

Common questions

Can it post to Microsoft Teams instead?

Yes. Swap the Slack module for a Teams module; the Drive, Docs, and Claude steps do not change.

Can it tag people for their action items?

With a bit more setup, yes, by mapping owners to Slack mentions. Start with a plain recap, then add mentions.

What if I want it in a thread, not the channel?

Slack modules can post to a thread if you provide the thread reference. The simple version posts to the channel.

Does it keep the transcript?

Yes. The transcript stays in Drive; Slack gets the short recap built from it.

Is the chat app the same as the API?

Same models, different door. Make needs an API key from the console, not the chat login.

Primary sources

• Creating a scenario (Make Help)
• Claude API overview (Anthropic)
• Slack Help Center
• Claude on Make (integrations)
• Slack — Grokipedia

Last reviewed: May 2026. Make, Claude, Google, and Slack 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