How do you send HubSpot alerts to Slack via Make.com?

Quick Answer: You can send HubSpot alerts to Slack using Make.com by creating a scenario that watches for HubSpot triggers (such as new deals or pipeline stage changes) and posts a formatted message to a Slack channel. This gives you more flexibility than the native HubSpot-Slack integration, including dynamic channel routing and custom message formatting.

The native HubSpot-Slack integration covers the basics. But if you want alerts that go to different channels based on deal owner, pipeline stage, or deal value, you need something more flexible. Make.com fills that gap. This tutorial walks you through building a HubSpot to Slack alert scenario from scratch, covering new deal notifications and pipeline stage updates.

What You Need Before You Start

Before building the scenario, make sure you have the following in place:

• A Make.com account (free tier works for this)
• A HubSpot account with CRM access
• A Slack workspace where you have permission to add apps
• At least one Slack channel set up for deal or pipeline notifications

You do not need any coding experience. Make.com uses a visual, node-based builder.

How to Connect HubSpot and Slack in Make.com

Step 1: Create a new scenario

Log into Make.com and click Create a new scenario from your dashboard. You will land on a blank canvas with a prompt to add your first module.

Step 2: Add HubSpot as your trigger module

Click the large + icon and search for HubSpot CRM. Select it, then choose your trigger event. For new deal alerts, select Watch Objects and choose Deals as the object type.

If you have not connected HubSpot to Make.com before, you will be prompted to authorise the connection. Click Add next to the connection field and follow the OAuth flow. Make.com will redirect you to HubSpot, where you grant access. Once authorised, your connection appears in the dropdown.

Configure the trigger settings:

• Watched fields: Select the fields you want to monitor (for example, deal name, amount, pipeline, deal stage, owner)
• Limit: Set how many records to process per run (10-20 is a sensible starting point)

Step 3: Add a Slack module

Click the + icon after your HubSpot trigger to add a second module. Search for Slack and select Create a Message.

Authorise your Slack connection the same way you did for HubSpot. If you are already using HubSpot more deeply for automation and reporting, it can also be worth reviewing some of the best B2B SaaS HubSpot agencies if you need help beyond simple alert workflows. You will be asked to choose which Slack workspace to connect.

Once connected, configure the message:

• Channel: Select the Slack channel where alerts should post
• Text: Build your message using HubSpot data from the previous module

How to Format Your HubSpot Deal Alert Message

This is where Make.com separates itself from the native integration. You can build a message using any field from the HubSpot deal record.

A clear, useful deal alert message includes:

• Deal name
• Deal value
• Pipeline and stage
• Deal owner
• A direct link to the HubSpot record

In the Text field of the Slack module, click inside the field and use the mapping panel on the right to insert HubSpot variables. A working template looks like this:

New Deal Created

Name: [Deal Name]
Value: [Amount]
Pipeline: [Pipeline]
Stage: [Deal Stage]
Owner: [Owner Name]

View in HubSpot: [Deal URL]

Replace each bracketed item with the corresponding mapped field from your HubSpot trigger module. Make.com displays all available fields from the deal record in the mapping panel.

How to Build a Pipeline Stage Update Alert

New deal alerts are straightforward. Pipeline stage change alerts require one additional step: a filter.

Step 1: Use the same HubSpot trigger

Keep the Watch Objects (Deals) trigger from the previous setup. Make sure Deal Stage is included in your watched fields.

Step 2: Add a filter between HubSpot and Slack

Click the small wrench icon on the arrow between your HubSpot and Slack modules, then select Set up a filter. This tells Make.com to only continue to the Slack step when a specific condition is met.

Set the filter condition:

• Label: Stage Changed
• Condition: Deal Stage > Does not equal > [leave blank, or set to a specific stage you want to exclude]

For a more targeted alert (for example, only when a deal reaches "Proposal Sent"), set the condition to:

• Deal Stage > Equal to > Proposal Sent

You can stack multiple conditions using AND/OR logic if you want alerts for several stages.

Step 3: Customise the Slack message for stage updates

Update your Slack message template to reflect the context of a pipeline update:

Pipeline Update

[Deal Name] has moved to [Deal Stage]
Value: [Amount]
Owner: [Owner Name]

View deal: [Deal URL]

How to Route Alerts to Different Slack Channels

The native HubSpot-Slack integration only supports static channel selection. Make.com lets you route alerts dynamically based on deal data.

To send alerts to different channels based on deal owner or pipeline:

Option 1: Use a Router module

After your HubSpot trigger, add a Router module (found under Flow Control). A Router splits your scenario into multiple branches, each with its own filter and Slack module.

• Branch 1: Filter by Owner = Sales Rep A, post to #sales-rep-a
• Branch 2: Filter by Owner = Sales Rep B, post to #sales-rep-b
• Branch 3: Filter by Pipeline = Enterprise, post to #enterprise-deals

Each branch has its own Slack module with its own channel setting.

Option 2: Use a variable channel name

If your Slack channels follow a naming convention tied to HubSpot data (for example, a channel per sales rep), you can map the channel field dynamically using a formula. In the Slack module's Channel field, use a text formula to construct the channel name from the deal owner's name.

This approach requires your Slack channels and HubSpot owner names to follow a consistent format.

How to Schedule and Test Your Scenario

Set your scenario schedule

Make.com scenarios can run on a schedule or be triggered instantly using webhooks. For deal alerts, set the scenario to run every 5 or 15 minutes. Click the clock icon at the bottom of the canvas to set the interval.

For real-time alerts, replace the Watch Objects trigger with a HubSpot webhook trigger. This requires a paid HubSpot plan but fires the scenario the moment a deal is created or updated.

Test before you go live

Click Run once in the bottom left of the canvas. Make.com will execute the scenario once using live data from HubSpot. Check the output of each module by clicking the bubble above it. You will see exactly what data passed through and whether the Slack message posted correctly.

If the Slack module shows a success indicator (a green tick with a number), check your Slack channel. Your test alert should be there.

Common Errors and How to Fix Them

HubSpot connection returns no records
Check that your HubSpot trigger is watching the correct object type and that deals exist in the pipeline you are monitoring. Also confirm the date filter is not excluding recent records.

Slack message posts but fields are blank
This means the HubSpot fields were not mapped correctly. Go back to the Slack module, click inside the Text field, and re-map each variable from the HubSpot module output. Do not type field names manually.

Filter is blocking all records
Open the filter and check the condition logic. A common mistake is using "Equal to" when the field value in HubSpot uses a different format (for example, internal stage IDs rather than display names). Use Make.com's data inspector to check the exact value coming through.

Scenario runs but no Slack message appears
Confirm the Slack channel name is correct and that your Make.com Slack connection has permission to post to that channel. Private channels require the Slack app to be invited first.

Why Use Make.com Instead of the Native HubSpot-Slack Integration?

The native HubSpot-Slack integration (built directly into HubSpot's settings) works well for basic notifications. It falls short when you need:

• Alerts routed to different channels based on deal data
• Custom message formatting with specific fields
• Conditional logic (for example, only alert when deal value exceeds £10,000)
• Alerts triggered by specific pipeline stage changes rather than all updates
• Notifications that also trigger other actions (for example, creating a task in Asana or logging to a Google Sheet)

Make.com handles all of these without writing a single line of code. At SaaS Hackers, this is the setup we recommend for any sales team running more than one pipeline or managing deals across multiple reps. If you are comparing broader partner options for CRM automation, RevOps, or growth systems, our lists of B2B SaaS inbound marketing agencies and B2B SaaS marketing ops agencies are a useful next step.

FAQs

What is the difference between Make.com HubSpot-Slack alerts and the native integration?
The native HubSpot-Slack integration sends notifications to fixed channels and covers a limited set of triggers. Make.com lets you build conditional logic, route alerts to different channels based on deal data, format messages with any HubSpot field, and chain additional actions after the Slack message posts.

Can I send HubSpot deal alerts to a private Slack channel using Make.com?
Yes. You need to invite the Make.com Slack app to the private channel first. Open the channel in Slack, type /invite @Make (or the name of your connected app), and confirm. After that, the private channel appears in Make.com's channel dropdown.

How often does Make.com check HubSpot for new deals?
On Make.com's free plan, the minimum interval is 15 minutes. Paid plans allow 1-minute intervals. For real-time alerts, use a HubSpot webhook as the trigger instead of the Watch Objects polling trigger. This fires the scenario instantly when a deal is created or updated.

Do I need a paid HubSpot plan to use Make.com for Slack alerts?
No. The Make.com HubSpot integration works with free and starter HubSpot accounts using the Watch Objects trigger. Real-time webhook triggers require a HubSpot plan that supports webhooks (Professional or above), but polling-based scenarios work across all HubSpot tiers.

Can Make.com send different Slack messages depending on the deal value?
Yes. Add a filter or router module between the HubSpot trigger and the Slack module. Set the condition to check the deal amount field (for example, Amount greater than 10000) and configure a separate Slack message for each value range. Each branch can post to a different channel with a different message format.