Connect HubSpot and Slack With Make: Route Every Deal Update to the Right Person Automatically

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 does a good job tracking where a deal is, but it does not automatically tell the right people when something changes. Teams end up relying on manual checks, spreadsheet exports, or the person who happened to notice. HubSpot's own research suggests that sales teams using integrated tools see up to 27 percent faster response times on deal-stage changes, yet most teams still rely on someone remembering to check.

Make can bridge that gap in about 30 minutes. It watches your HubSpot deal pipeline and sends the right message to the right Slack channel or person the moment a stage changes. No developer needed. No new tools. Just the ones you already have.

Step 1: Set up the Make connection to HubSpot

Log into Make and create a new scenario. Search for the HubSpot module and select "Watch Deals" as your trigger. Make will ask you to authenticate with your HubSpot account.

Scenario: HubSpot Deal Router
Trigger: HubSpot > Watch Deals
- Pipeline: [your sales pipeline]
- Watch: Deal stage changes only
- 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 "Watch Deals" module tracks all deal changes by default. You want to filter it down to the stage changes that actually matter.

Filter: Deal stage changed from [Previous Stage] to [New Stage]
Conditions to route:
- 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 only proceed when the deal stage field has changed. This stops the workflow from firing on every contact update or note addition that happens inside a deal.

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.

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 when it's wired

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.

This single workflow handles deal routing for every stage your pipeline has. You can extend it later to include 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. HubSpot data from 2025 shows that teams using automated CRM-to-Slack notifications close deals 19 percent faster than teams relying on manual updates, and the average response time to a stage change drops from 8 hours to under 10 minutes.

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 documentation 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. If you want to see how this fits into a larger automation stack, speak with us about a two-week pilot.