Email to Slack: Claude + Make

A three-person property-management team shares one inbox. A burst pipe email and a flyer for printer toner land in the same list, and the urgent one waits four hours because everyone assumed someone else saw it. The shared inbox is where accountability quietly disappears.

This build turns the inbox into a feed the team actually watches. When an email arrives, Claude writes a one-line summary, tags the topic, and rates the urgency, then Make posts that to a Slack channel. The full email still lives in Gmail; Slack carries the signal, so nobody has to camp in a shared inbox to catch the pipe.

We build it in Make. It is a cousin of our draft-replies guide: same Gmail trigger, same Claude brain, but the output goes to a team channel instead of your drafts. The judgment Claude adds here is triage, not writing.

What does this workflow actually do?

In one line: a new email becomes a tidy Slack message. Make watches your inbox. When an email arrives, Claude summarizes it and tags topic and urgency, and Make posts that summary to a Slack channel. The email stays in Gmail; the team reads the signal in Slack.

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

• The property-management team above, never again sitting on a burst-pipe email.
• A volunteer animal shelter whose adoption inbox belongs to everyone and therefore no one.
• A food co-op board that wants member emails summarized into the channel they already check.
• A freelance video-editing collective sharing a clients inbox across three time zones.

Reading every email to find the one that matters is the tax a shared inbox charges. Claude pays it for you and hands the team a sorted feed.

Why use Make if Claude can already write?

Reasonable question. Claude is good at reading an email and saying, in one line, what it is and how urgent it is. It is not built to watch the inbox, post to Slack, and run on a schedule. That is plumbing, and Make handles plumbing.

Make does the no-judgment steps: catching each email, posting to the channel, running on its own. Claude does the one step that needs reading and judgment, the summary and the urgency call. Make is the wire; Claude is the triage nurse on the end of it. I built a version that asked the AI to also decide which channel and ping people, and it overreached; keeping Claude to summarize-and-tag and letting Make route is what kept it trustworthy.

What do you need before you start?

• A Make account. The free 1,000 operations a month covers a busy shared inbox.
• A Claude API key from the console, not the chat app. See how to use Claude.
• A Gmail account, ideally with one label for the mail you want triaged.
• A Slack workspace and a channel to post into, with permission for the connection to post there.

Two Make words. A scenario is the whole inbox-to-Slack automation. A module is one box. Three boxes, one scenario.

How does the workflow work, step by step?

Three modules, left to right:

Module	App	What it does
1. Trigger	Gmail	Watches the inbox and fires on each new email
2. Brain	Claude	Summarizes the email and tags topic and urgency
3. Output	Slack	Posts the summary into a team channel

Step 1: Watch Gmail for new mail

Create a scenario and add Gmail, Watch emails. Connect your account and point it at the label you want triaged so the channel does not fill with newsletters. This trigger hands the next step the sender, subject, and body.

Step 2: Let Claude summarize and tag it

Add a Claude module, Create a Prompt, paste your key, pick Sonnet. Give it clear rules so the urgency call is consistent:

Summarize this email for a busy team channel.
From: {{sender from Step 1}}
Subject: {{subject from Step 1}}
Body: {{body from Step 1}}

Return three lines:
Summary: one sentence, plain.
Topic: one of billing, maintenance, sales, member, other.
Urgency: high only if money or safety or a deadline is at stake,
else medium or low. Nothing else.

Spelling out what counts as high urgency is the difference between a useful feed and one where everything screams.

Step 3: Post it to Slack

Add Slack, Send a Message, connect Slack, pick your channel, and map Claude’s three lines into the message along with the sender. To cut noise further, you can add a Make filter so only high-urgency items post, or route each topic to its own channel. Always keep the full email in Gmail; Slack is the alert, not the archive.

How do you run it and check the result?

Click Run once. Make takes a recent email, Claude summarizes and tags it, and the message lands in your Slack channel. Read it. When I tested this, the summary was solid immediately and the urgency tag was right most of the time, which is exactly what you refine by tightening the criteria in Step 2. Once the tags match your judgment, switch the scenario on.

After that, the team stops scanning a shared inbox and starts reading a sorted feed. The burst-pipe email arrives in the channel tagged high, next to the toner flyer tagged low, and the difference is obvious at a glance.

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 short summary on Sonnet costs a fraction of a cent
Gmail	Free	Free
Slack	Free plan works	Paid plans from about $7/user/month

Each email is three Make operations and a sliver of Claude. A filter that posts only high-urgency items keeps both the channel and your operation count low. More on tiers in our Make guide.

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

• Everything gets tagged high. Spell out in the prompt what high actually means. This was the main thing I tuned.
• Newsletters flood the channel. Filter the Gmail trigger by label so only real mail is triaged.
• The channel gets noisy. Add a Make filter for high-urgency only, or split topics across channels.
• Slack rejects the post. Check that the Slack connection has permission to post in that channel.

The same shape powers a lot of routing builds. See more in Make AI scenarios.

How do you build this in Zapier or n8n instead?

Same three jobs, different names.

Job	Make	Zapier	n8n
Catch an email	Watch emails	New Email trigger	Gmail Trigger node
Summarize and tag	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. n8n is the self-hosting pick. Full comparison: Zapier vs Make vs n8n.

Frequently asked questions

Can it post only urgent emails?

Yes. Add a Make filter after Claude so only items tagged high pass through to Slack. The rest stay quietly in Gmail.

Will the team lose the full email?

No. The email stays in Gmail untouched. Slack gets the summary; you open Gmail when you need the detail.

Can different topics go to different channels?

Yes. Use the topic tag in a Make router so maintenance goes one place and billing another.

Does it work with Microsoft Teams?

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

Is the chat app the same as the API?

Same models, different access. The app is for chatting; Make needs an API key from the console.

Sources and official docs

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

Last reviewed: May 2026. Make, Claude, Gmail, and Slack update their interfaces; verify button names on the official pages.

You may also like

• Draft WordPress posts from a spreadsheet with Claude + Make
• Turn a YouTube video into a WordPress draft with Claude
• Turn a blog post into LinkedIn and X posts with Claude
• Make AI Scenarios: automations that save hours
• How to use Claude AI
• Zapier vs Make vs n8n: which to start with
• The AI Tools Directory