# HubSpot Slack integration: three deal alerts a sales manager needs, and what to mute https://salesbond.app/blog/hubspot-slack-integration-deal-alerts/ Published: 2026-10-20 · Updated: 2026-10-20 Connect HubSpot to Slack from the HubSpot Marketplace (a Super Admin or a user with App Marketplace permissions, who is also a Slack workspace administrator), then send only three deal alerts to the sales channel: a stage move into a late stage, a deal that has gone quiet, and closed-won. The HubSpot Slack app has no built-in alert for a deal changing stage or going quiet; all three alerts are sent with the “Send a Slack notification” workflow action, and workflows need a Professional or Enterprise subscription ( [HubSpot: Manage notifications in Slack](https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack)). The app’s own notifications cover mentions, form submissions, tasks, live chat and activity logged on a record. Everything else that could post to the channel, you leave off. ## What the HubSpot Slack app does, and what it does not HubSpot’s own description of the app is short: once connected, you can manage HubSpot records from Slack, receive notifications, share HubSpot data with the team, and use Breeze Assistant in Slack to summarize records and threads, create tasks and notes, and prepare for meetings ( [HubSpot: Connect HubSpot and Slack](https://knowledge.hubspot.com/integrations/how-do-i-use-the-slack-integration)). Workflows can also create a Slack channel for a deal or company and post a custom message with action buttons ( [HubSpot: Manage notifications in Slack](https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack)). What it does not have is a “deal alerts” screen. We went looking for one, because that is the screen a manager expects to find. The notification settings (Settings > Notifications > Other apps) let a user route their own HubSpot notifications to Slack: mentions on records, form submissions, task assignments and reminders ( [HubSpot: Manage notifications in Slack](https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack)). Those are personal. They go to the HubSpot app in Slack, to one person, and they say nothing about pipeline movement. The second built-in option is closer. Associate a deal record with a Slack channel and any new call, note, email, task or meeting logged on that deal posts to the channel (same page). That is the right tool for one large deal with a war room. It is the wrong tool for a team channel, because thirty deals times every logged email is a channel nobody reads by Thursday. So the honest architecture is this: personal notifications stay personal, record channels are for the two or three deals that deserve one, and the team channel gets three workflow messages. ## Who can install it A HubSpot Super Admin or a user with App Marketplace permissions installs it, and that person must also be an administrator of the Slack workspace; if they are not, they ask the Slack admin to grant access ( [HubSpot: Connect HubSpot and Slack](https://knowledge.hubspot.com/integrations/how-do-i-use-the-slack-integration)). So it is two hats on one head, or two people in one meeting. The sales manager rarely has the Slack hat so book fifteen minutes with whoever runs Slack rather than discovering the gap halfway through. The install itself, per the same help page: 1. In HubSpot, click the Marketplace icon in the top navigation bar and select HubSpot Marketplace. 2. Search for Slack and select it. 3. Click Install. Slack opens in a new browser tab. 4. Review the requested permissions and click Allow. 5. Back in HubSpot, look for the confirmation email from Slack that the HubSpot app is installed in your workspace. Two limits to know before you click. Only one Slack workspace can be connected through this integration, so a company with a sales workspace and a separate “everyone” workspace has to choose. And the app asks for access to public and private channel content, which HubSpot says is there to support live chat with website visitors. Your Slack admin will ask about that line, so have the answer ready. Turn on one more thing the same day: the Approved Apps setting in Slack, which HubSpot recommends because it stops non-administrators from removing the HubSpot app from inside Slack. An integration that quietly disappears is worse than one that never existed, because the team reads the silence as “nothing is happening”. ## Three HubSpot Slack notifications a sales manager needs We think a sales team channel should carry three kinds of message from HubSpot and no more. Each one answers a question the manager would otherwise ask in the 1:1, and each has a reply the rep can give in under a minute. ![Three Slack alert cards: stage move, quiet deal, closed-won, each with its HubSpot trigger, who is mentioned and the expected reply](https://salesbond.app/wp-content/uploads/2026/10/hubspot-slack-integration-deal-alerts-2.png) **Stage move into a late stage.** A deal-based workflow that enrolls deals when Deal stage is one of your late stages (ours are Proposal sent and Negotiation), with the action Send a Slack notification. The message text is yours to write. HubSpot lets you include deal properties and at-mention a user ( [HubSpot: Manage notifications in Slack](https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack)), so add Deal name, Amount, Close date and the owner. The reply we ask for is one line: the next step and its date. If the rep cannot write that line, the deal was moved too early and the channel has just told you so, no report needed. **A quiet deal.** By “quiet” we mean an open late-stage deal whose Last activity date is older than your threshold. That is the trigger from [the HubSpot workflow that tasks the owner when a deal goes quiet](https://salesbond.app/blog/hubspot-workflow-stale-deal-task/). That article builds the task; here you add a second action to the same workflow, a Slack message to the deal owner. Don’t post this one to the whole channel. The action can notify individual users, channels, or the record’s existing owners, and “existing owners” is the right choice, because a public list of quiet deals turns into a public list of whose deals are quiet. Reply expected by the end of the working day: what happened, and what is next. **Closed-won.** Trigger: Deal stage is Closed won. Post to the team channel, no at-mention, with Deal name, Amount and owner. No reply needed. This is the one alert people want to see, and its the reason they don’t mute the channel that carries the stage moves. The same action can put buttons on the Slack message. HubSpot’s list includes Create task, Log call, Log email and Update [object], which in a deal-based workflow opens a form with the deal properties from your deal create form (same page). Add Create task and Update [object] to the quiet-deal message; a rep who can fix the deal from Slack usually does. Leave the buttons off the closed-won post. ## Mapping emails so the alert reaches a person An at-mention only works if HubSpot knows which Slack user the deal owner is. It matches on email. If the HubSpot user email matches the Slack one, notifications arrive on their own; if not, the user gets an email and an in-app notification asking them to map the addresses, and the confirmation in Slack has to happen within 24 hours ( [HubSpot: Connect HubSpot and Slack](https://knowledge.hubspot.com/integrations/how-do-i-use-the-slack-integration)). Here is the catch for the manager. The workflow’s “Send notification to users” dropdown only lists users who have mapped their email addresses ( [HubSpot: Manage notifications in Slack](https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack)). A rep who is firstname@ in HubSpot and f.lastname@ in Slack is invisible to the picker. Nothing errors. The deal stays quiet, the alert never lands, and the rep says, truthfully, that they were never told. So treat mapping as a roll call, not an admin task. Before the first workflow goes live, open the user dropdown and count the names against the team list, anyone missing does the 24-hour verification that day. Check private channels at the same time. The HubSpot app has to be added to a private channel first, and until it is, the workflow’s channel picker will not show that channel. ## One channel, one owner per workflow The channel agreement matters more than the workflows, and ours fits in the channel topic: *This channel carries stage moves and wins from HubSpot. If you are mentioned, reply in the thread with the next step and a date before the end of the working day. Nobody is expected to read it on the weekend.* The end-of-day rule is the part people get nervous about, so say why: a stage move with no next step is the earliest point a drifting deal can be caught, and a thread reply is cheaper than the same question in Monday’s meeting. Each workflow also gets one named owner in its description. When a stage gets renamed and a trigger stops matching, the owner is the person who notices. Without one, someone finds out by accident, months later. Per-deal channels are a separate tool. A workflow can create one and invite users; the name has to be 80 characters or less, in lowercase letters, numbers, hyphens and underscores, and a private channel made this way is visible only to the user who owns the enrolled record (same help page). We keep them for deals above a size the team agrees on and archive them when the deal closes. ## The weekly review: share the report, not the screenshot HubSpot can post reports and dashboards to Slack, which replaces the Monday screenshot someone used to paste at 08:55. From a dashboard, Actions > Share to Slack posts the reports once to a channel, with an optional message. An individual report goes through Actions > Share via > Slack, and there you can make it recurring (daily, weekly or monthly) at a time you choose ( [HubSpot: Share or export reports and dashboards](https://knowledge.hubspot.com/dashboard/email-or-export-reports-and-dashboards)). Three limits decide whether this is useful. Reports can only go to public Slack channels, not shared ones. Report data is captured two hours before the send time, so a 09:00 post shows the pipeline as of 07:00, and a rep who updated a deal at 08:30 will say the numbers are wrong. And the link in Slack only opens for people who already have access to the report in HubSpot (same page), which brings you back to [who can see the sales dashboard and who can break it](https://salesbond.app/blog/hubspot-dashboard-sales-manager-setup/). Our setup is one weekly recurring share of the report the pipeline meeting starts with, Monday morning, an hour before the meeting. Not daily. A daily post is the fastest way we know to get a channel muted, and the closed-won posts die with it. Only a Super Admin or the dashboard’s owner can edit or delete a recurring message (same page), so make sure that owner is someone who still works there. ## Alert fatigue: what to switch off The failure we would watch for is not a missing alert but too many of them. The team channel carries new deals, every stage move from the first stage upward, every note, every task, and a report nobody opens. Before long half the reps have muted it, and the manager can’t tell a quiet week from a muted channel. ![Two-column sorting: three alerts go to the sales channel, everything else stays in HubSpot or goes to one person](https://salesbond.app/wp-content/uploads/2026/10/hubspot-slack-integration-deal-alerts-3.png) Most of what to switch off is one decision each. Personal notifications routed to Slack live under Settings > Notifications > Other apps, and each user sets thier own; our default is task reminders on and the rest left in HubSpot. Form submissions in a sales channel are a marketing conversation anyway. Don’t associate every deal with the team channel, because every logged email will follow. Skip a “new deal created” workflow: creating a deal is not news, a deal reaching Proposal sent is. Leave early stage moves alone, so in a seven-stage pipeline the alert fires on two stages, not six. And the quiet-deal alert goes to the owner, never to the channel. A disclosure, since this is where a manager starts wondering whether the channel can replace a pipeline review. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It analyses deal data in the CRM, finds risks and explains what needs attention, so the manager works from one list instead of scrolling a channel. The three alerts above still belong in Slack, because the rep needs the nudge the same day. [Check your CRM with SalesBond](https://salesbond.app/) if you want that list without building the filters. ## Monday check Five minutes before the pipeline meeting, with the channel and HubSpot open side by side: 1. Scroll the channel back seven days. Compare the stage-move posts with the deals that actually entered late stages this week (the [saved view of deals without a next activity](https://salesbond.app/blog/hubspot-deals-without-next-activity-saved-view/) is a quick cross-check). A gap means a trigger or a stage name changed. 2. Every stage-move mention has a threaded reply with a next step and a date. The ones without one are the first three minutes of the meeting. 3. Open the quiet-deal workflow and look at enrollments. Zero in a team with late-stage deals is a broken trigger, not a perfect team. 4. Check the workflow’s user dropdown against the team list. A new hire who hasn’t mapped their email is receiving nothing. 5. The Monday report arrived, in the right channel. If the check takes longer than five minutes, the channel is carrying too much and the fix is in the section above, not in another workflow. The Pipedrive version of this setup is in [a quiet Slack channel for deals](https://salesbond.app/blog/pipedrive-slack-deal-alerts-automation/): same alerts, different plumbing.