Your sales team closes a deal at 4pm on a Friday. The account manager does not find out until Tuesday. The handoff was supposed to happen in HubSpot, but nobody checked the deal stage column. By the time someone follows up, the customer has already emailed support with a question no one was ready for.
This is the problem with deal updates that live inside a CRM and nowhere else. HubSpot tracks where a deal is well, but it cannot tell the right people when something changes. A HubSpot Slack integration built with Make closes that gap in about 30 minutes. It watches the deal pipeline and posts the right message to the right Slack channel or person the moment a stage changes.
HubSpot ships a native Slack app, and it handles the everyday jobs well. You can turn a Slack message into a task, log a note against a contact, and get notified when a ticket arrives. Deal routing is a different job. When a deal moves from proposal to negotiation, the message needs to land in the right channel with the owner tagged, and the channel, wording and recipient often change with the stage, region or deal size. That is where Make earns its place. It adds the routing logic the native app leaves out, using the HubSpot and Slack accounts you already have.
Manual checking survives because the week fills up fast. Salesforce's 2026 State of Sales report, based on 4,050 sales professionals, found reps spend only 30% of an average week selling. Another 9% goes to administrative tasks, and 9% to manually entering customer and sales information. A deal router removes one of those loops. Nobody has to open the CRM to learn a deal moved.
Accounts and access
- A Make account (the free tier covers this workflow)
- A HubSpot account with deal pipeline data
- A Slack workspace where you can create channels and webhooks
- About 30 minutes
Step 1: Set up the Make connection to HubSpot
Log into Make and create a new scenario. Search for the HubSpot CRM module and choose a trigger. Watch Deals fires when a new deal is created. If you want stage moves on existing deals as well, pick Watch CRM Objects and set the object type to Deal. Make will ask you to authenticate with your HubSpot account.
Scenario: HubSpot Deal Router Trigger: HubSpot CRM > Watch CRM Objects (Deals) - Pipeline: [your sales pipeline] - Watch: created and updated deals - Limit: 10 (keeps the first webhook call small for testing)
When you connect Make to HubSpot for the first time, it pulls a list of your pipelines and stages. Pick the pipeline your sales team actually uses. If you have multiple pipelines, you can duplicate the workflow later for each one.
Step 2: Configure the deal stage trigger
The trigger fires on deal activity, not only stage moves. You want to act only on the stage changes that matter to your team.
| Deal stage change | Where it routes |
|---|---|
| New lead qualified | #leads-incoming (SDR team) |
| Proposal sent | #deals-in-progress (account execs) |
| Negotiation started | #deals-in-progress + @deal-owner |
| Closed won | #wins (everyone) |
| Closed lost | #losses (deal owner + manager) |
Create a filter in Make right after the trigger. Set it to let deals through only when the stage matches one of the rows above, for example Proposal Sent or Closed Won. This stops the workflow from firing on note additions, contact updates and other deal activity that does not need a Slack ping.
Step 3: Build the Slack message template
Add a Slack module to your scenario. Select "Send a Message to a Channel" as the action. Make will ask you to authenticate with your Slack workspace.
The message template pulls data directly from HubSpot using Make's mapping panel. Click into each field and select the HubSpot deal property you want to include.
Message template:
[Stage Emoji] Deal Update: {{deal.name}}
Stage: {{deal.stage}} → {{deal.new_stage}}
Value: {{deal.amount}}
Company: {{deal.company}}
Owner: {{deal.owner}}
Next step: {{deal.next_step || "Not set"}}
Keep the message short enough to scan on mobile. A deal update that takes three scrolls to read will get ignored. Use stage emojis so your team can identify the type of update at a glance without reading the text.
Step 4: Route to the right channel and person
This is where Make's router tool comes in. Add a Router module after the Slack connection and create separate routes for each deal stage outcome.
Router paths: Path 1: Stage = "Qualified to Connect" → #leads-incoming Path 2: Stage = "Proposal Sent" → #deals-in-progress Path 3: Stage = "Negotiation" → #deals-in-progress + @deal-owner Path 4: Stage = "Closed Won" → #wins Path 5: Stage = "Closed Lost" → #losses + @deal-owner
Each path gets its own Slack module with a different channel and message template. Use Make's text parser to extract the deal owner's Slack handle from your team directory, or keep it simple and tag them by their HubSpot user email.
Pro tip: Create a dedicated #sales-updates channel for the routing workflow. Your team can mute it during deep work and check it between meetings. The signal-to-noise ratio stays high because every message is a stage change that matters.
Step 5: Test and iterate
Before you turn the workflow on, run it with a test deal. Move a deal through your pipeline stages in HubSpot and watch the Slack messages arrive in real time.
Things to check in your test:
- Does each stage change fire the right Slack message?
- Is the deal owner tagged correctly?
- Are the stage emojis and formatting readable on mobile?
- Does a rapid double-stage change (e.g. proposal to negotiation in one edit) fire once or twice?
Once the test passes, schedule the scenario to run every 5 to 15 minutes depending on your deal volume. Most teams with fewer than 50 active deals can run it on a 15-minute interval without hitting any Make rate limits.
What changes once your HubSpot Slack integration is live
Your team stops checking HubSpot for updates and starts reacting to them. The account manager who finds out about the Friday 4pm close on Monday now knows about it at 4:05pm, because the #wins channel pinged their phone.
Trust plays a part too. Salesforce's most recent State of Data and Analytics research found only 35% of sales professionals completely trust the accuracy of their organisation's data. When people doubt the numbers in the CRM, they check it less often. A Slack message with the deal name, value and owner makes the update visible without a login.
This single workflow handles deal routing for every stage your pipeline has. You can extend it later with deal-value thresholds that route high-value deals to a separate channel, or region-based routing that sends EMEA deals to the London team and APAC deals to the Sydney team. We could not find a credible public benchmark that measures CRM-to-Slack routing specifically. Most of the numbers floating around trace back to vendor marketing. What this workflow changes is measurable in your own pipeline. Track the time from a stage change to first response, and count the updates that get missed entirely.
The same pattern works for any CRM with a Make module. We have built similar workflows for lead qualification with Claude and n8n and for AI email nurture with Claude and HubSpot. The principle is the same. Connect the tools your team already uses, remove the manual check, and let the right information find the right person.
Frequently asked questions
What do I need to set this up?
You need a Make account (free tier works), a HubSpot account with deal pipeline access, and a Slack workspace where you can create channels and webhooks. No credit card needed for the Make free tier, and Make's HubSpot and Slack integration page covers the authentication process step by step.
Can I route to individual people instead of channels?
Yes. Make can look up the deal owner from HubSpot and send a direct Slack message to that person, or use @mentions in channel messages. The Slack module documentation shows how to send direct messages via Slack's API.
How long does it take to set up?
The basic workflow takes about 30 minutes. Routing to multiple channels with conditional logic takes another 15 to 20 minutes. Most of the time is spent on the first setup because you are mapping HubSpot fields into Slack message templates for the first time.
What deal stages should I route?
Focus on the stage changes that need human attention: new qualified leads, proposals sent, negotiations started, won deals, and especially lost deals. Lost deals need the fastest response because that is when a competitor call or retention conversation needs to happen.
Does this work with Pipedrive or Salesforce too?
Yes. Make has native modules for Salesforce, Pipedrive, and most major CRMs. The workflow pattern is the same regardless of which CRM you use. We wrote up the same routing logic for MQL to SQL handoff with Pipedrive and Zapier. If you want to see how this fits into a larger automation stack, speak with us about a two-week pilot.