Make.com Slack Integration

Make.com Slack Modules

Make.com has native Slack modules covering:

Triggers:

• Watch New Message (in a channel)
• Watch File Shared
• Watch New Event (slash commands, button clicks)

Actions:

• Create a Message (send to channel or DM)
• Update a Message (edit an existing message)
• Add a Reaction (emoji reaction to a message)
• Upload a File
• Search for Message
• Get User Information
• Invite User to Channel

These modules cover most Slack automation use cases without needing the Slack API directly.

Slack as a Notification Destination

The most common Make.com + Slack pattern: send a Slack message when something important happens. Slack becomes the real-time notification layer for all your automated workflows.

Best practices for Slack notifications:

Use Block Kit formatting: Plain text messages are hard to scan. Format messages with bold headers, code blocks, and field/value layouts. Make.com's Slack module accepts Block Kit JSON for rich message formatting.

Include actionable information: A good Slack alert includes: what happened, key data, and what (if anything) needs to be done. "New lead: John Smith at Acme Corp (ICP Score: 87). Call within 2 hours." beats "New lead received."

Use the right channel: Route alerts to appropriate channels (not everything to #general). Sales alerts → #sales-leads. Engineering issues → #engineering-alerts. Billing events → #billing.

Common notification triggers:

• New high-priority lead created in HubSpot
• Support ticket at-risk SLA
• Large order placed in Shopify
• Low inventory alert
• Failed scenario execution
• Weekly/daily metric digest

Slack as a Trigger

Less common but powerful: Make.com triggered by Slack messages.

Slash commands: Configure Slack to route a custom slash command to a Make.com webhook. /runreport → triggers a Make.com scenario that fetches and posts the weekly report in the channel.

Message keywords: Watch a specific channel for messages containing keywords. Someone posts "URGENT" in #support → Make.com triggers an escalation scenario.

File shared: When a file is shared in a specific channel → Make.com downloads and processes it. Finance team drops an invoice in #invoices → Make.com extracts data and enters it in the accounting system.

Interactive Slack Workflows

Slack's Block Kit supports interactive elements (buttons, dropdowns) that can trigger Make.com webhooks:

Approval flow:

1. Make.com posts a message with "Approve" / "Reject" buttons (Block Kit JSON)
2. Employee clicks "Approve" → Slack sends a webhook to Make.com with the action data
3. Make.com processes the approval → updates the relevant system

Quick data entry:

1. Make.com posts a message asking for missing data with a "Fill In" button
2. Button click opens a Slack modal form
3. Form submission → Make.com webhook receives the data and updates the record

Slack + AI Workflows

Combining Make.com, Slack, and Claude creates smart Slack bots:

Scenario: Answer questions from Slack

1. Slack trigger: Watch message in #ask-ai channel
2. Claude HTTP: Send the question + your knowledge base context to Claude
3. Slack Create Message: Reply in the thread with Claude's answer

Team members ask questions in Slack; the bot answers from your documentation.

Scenario: Summarise long threads

1. Slack trigger: Specific emoji reaction added to a message (e.g., 📋 "summarise this thread")
2. Slack API HTTP: Fetch all messages in the thread
3. Claude HTTP: "Summarise this Slack thread in 3 bullet points and identify any action items"
4. Slack Create Message: Reply in the thread with the summary

Alert Routing Best Practices

As your Slack workspace fills with automated notifications, organise them:

Create dedicated alert channels: #ops-alerts, #sales-alerts, #engineering-alerts. Route messages based on category — not everything to #general.

Use thread replies for follow-up: Post the initial alert to the channel; subsequent updates (resolved, escalated, handled) reply in the thread. Keeps the channel clean.

Add unfurl suppression: unfurl_links: false, unfurl_media: false prevents Slack from expanding URLs in automated messages, which can make channels noisy.

Throttle high-frequency alerts: For events that can trigger many times per minute (e.g., price updates), aggregate before posting — send one message per 5 minutes with all events, not one message per event.

Recommended Tools

• Make.com — Slack integration and automation
• Slack — Team communication and alert destination
• Claude API — AI answering Slack questions
• HubSpot — CRM events notified via Slack
• Stripe — Billing events notified via Slack
• PagerDuty — For critical alerting with on-call routing