Notifications are easy. Routing to the right channel is the part nobody built.
HubSpot Professional or Enterprise to create a channel from a workflow
Activities, Messages, Deals, Companies, events only.
Install it in five minutes, then meet the gap within a week. The workflow action sends to a channel you pick at design time. There is no built-in option to send to the channel associated with the deal that triggered the workflow, even when that association exists on the record. Teams solve it with one channel per segment, or by routing through n8n and calling the Slack API directly.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Workflow to channel | One way, out | Send Slack message is a workflow action. Any trigger can fire it: score threshold, stage change, deal gone quiet. |
| Record to channel association | Both ways | A deal or company record can be associated with a Slack channel, with per-activity-type notifications. |
| Channel creation | One way, out | A workflow can create a channel and associate it with the record. HubSpot Professional or Enterprise. |
| Slash commands | One way, in | Look up records and log activity from Slack, so the CRM gets updated by people who will not open it. |
One of those four rows moves in both directions. The three that do not are Workflow to channel, Channel creation and Slash commands, and those are the rows that decide how you design around this rather than the ones in the brochure.
There are no fields to map here. What there is instead is a set of surfaces, each with its own rule about where a message can go.
| In HubSpot | In Slack | What to know about the match |
|---|---|---|
| Workflow action | A fixed channel you pick | Static only. There is no option to send to the channel associated with the current record, which is the most requested thing on this pair. |
| Record association | The channel attached to that deal or company | Public channels, and private ones where the HubSpot app is a member. Activity types are chosen per association rather than globally. |
| Live chat and help desk conversation | An inbox channel | Routed per inbox, and a reply sent in the Slack thread still logs into the HubSpot inbox. |
| Personal notification | A direct message | Per user, configured by that user, and invisible to an admin who assumes they set it up for the team. |
| Slash command | A record lookup or a logged activity | The one direction that writes back, so the CRM gets updated without anybody leaving the conversation. |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: five field mappings and three documented exclusions, each one's note, and the two vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
Everything on that list is a routing rule rather than a data rule, which is why this pair is quick to connect and slow to get right.
Slack sets no plan gate on this integration, so the grid that matters is not editions: it is which HubSpot tier you hold against the kind of channel you are sending to. Pick one on each side and the grid marks the answer.
Pick one on each side.
| HubSpot tier | Public channel | Private, app added | Slack Connect |
|---|---|---|---|
| Free or Starter | Notifications and associations | Notifications and associations | Nothing |
| Professional | Plus workflow actions | Plus workflow actions | Nothing |
| Enterprise | Plus workflow actions | Plus workflow actions | Nothing |
Counted off that grid, of nine pairings: three give you nothing, two give you notifications and associations, four give you plus workflow actions. The free column is wider than people expect: the association, the notifications and the slash commands are all there, and Professional buys you the ability to make them a rule rather than a habit.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
HubSpot: Marketplace, Slack
Standard marketplace install and a Slack authorisation. If your workspace requires admin approval for apps, that approval is the long pole rather than anything in HubSpot.
Slack: the channel itself
Records can only be associated with public channels, and with private channels where the HubSpot app is already a member. A private deal room without the app in it simply will not appear in the picker, which reads as a bug and is not one.
HubSpot: Settings, Notifications, Other apps
Toggle Slack on under How you get notified, then pick what you want under What you get notified about. This is per user rather than account-wide, so a rollout means telling people to do it rather than doing it for them.
HubSpot: Connected Apps, Slack, General settings
Under Bring conversations to Slack, switch on the inboxes whose conversations should appear. Replies can go back through the Slack thread and still log in the inbox, which is the part that makes it worth doing rather than just an alert.
A company or deal record, Slack card in the right sidebar
Associate an existing channel or create one from the record, choosing visibility, a description and exactly which activity types notify. Doing this per record is deliberate: it is the only way to get a notification into the room where the deal is discussed.
HubSpot: Workflows
Workflows need Professional or Enterprise. The Slack action sends to a static, pre-selected channel, so if you want the message to land in the deal's own room you either use the record association above or branch the workflow once per channel.
The order matters in one place only, and it is the second step: adding the app to the private channels first turns the association step from debugging into picking from a list.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/hubspot-slack/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-slack.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyThe HubSpot app is not a member of it. Associations only work with public channels and private channels the app has been added to.
Add the app in that Slack channel, then refresh the record. No HubSpot setting substitutes for it.
WhyThe Slack workflow action takes a static channel. It cannot resolve the channel associated with the record being processed.
Use the record association for per-deal messages, or branch the workflow and give each branch a fixed channel. The second only scales to a handful of channels.
WhyThe Slack channel association comes from the primary record in a merge.
Associate the channel with the record you will keep as primary before merging, or choose the record that already has it as the primary.
WhyPersonal notification settings are per user, under Settings, Notifications, Other apps.
Tell people to turn their own on. An admin cannot do it for them, which makes this a rollout communication rather than a configuration task.
WhyEvery activity type was ticked when the channel was associated.
Re-open the association and uncheck everything that is not acted on. A muted channel is worse than no channel, because the team believes alerting works.
WhySlack Connect conversations are not covered.
There is no setting. Either keep deal discussion in an internal associated channel, or accept that the customer-facing thread is outside the record.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for this pair by name, in the words a person would use. 14 threads from 2020 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
Sounds cool in concept, but why would you want to do that with slack and not in HubSpot? I'm trying to understand the use case here
r/hubspot·February 2025·6 points
Because the people who need to see it are not in HubSpot. That is the entire case for this integration, and it is also the test for each notification you set up: if the person who needs it is already in the CRM that day, the notification is noise.
HubSpot doesn't expose Sales extension "email open" events as API webhooks or workflow triggers, which makes direct automation impossible. But here's the workaround that actually works: Instead of triggering off opens, trigger off engagement sequences that email opens create.
r/hubspot·November 2025·4 points
A practitioner's answer rather than a vendor statement, so treat it as a lead rather than a fact. It is worth testing against your own account before promising a manager the open notification they asked for, because the workaround changes what the alert actually means.
we've been working on a feature [...] that automatically syncs conversations happening on shared Slack channels (slack connect channels). All forms of communication (emails/sms/calls etc) are logged in HubSpot one way or other... but
r/hubspot·April 2025·6 points
Posted by somebody selling the fix, which is how you know the gap is real and how you should read the enthusiasm. Slack Connect conversations are outside this integration, and if a shared channel is where your customers actually talk to you, that is a hole worth pricing.
I have Hubspot connected to Slack, and I've added the Hubspot Slack user to the correct channel. I would like the Hubspot bot to post a message in this Slack channel anytime a new company is created on Hubspot.
r/hubspot·March 2020·4 points
That is a workflow with a Slack action, which needs Professional. Notice that the asker had already done the thing most people miss, adding the app to the channel, and still could not finish without the tier.
Our context is atomized: Linear for eng (source of truth, in theory), Slack for cross-team decisions/drive-bys, Figma for design comments + approvals
r/Slack·August 2025·5 points
Written by a head of product rather than a CRM admin, and it is the argument for configuring fewer notifications than the integration allows. Every activity type you tick is a vote against the channel being read at all.
The threads split cleanly between people asking how to get one specific event into a channel, and people asking why they should bother when the information is already in HubSpot. The first group runs into the same two walls every time: the workflow action will not follow the record, and some events cannot trigger a workflow at all. The second group is answered by where the reps actually are.
The useful filter from all of it: route the events somebody will act on in the next hour, and leave the rest in the CRM where they already are.
Slack is the step that decides whether the rest of the stack gets used. A pipeline that enriches, scores and routes a lead perfectly still fails if the first a human hears about it is tomorrow morning. That makes this the highest-leverage cheap integration in the directory and also the one teams configure worst.
The dynamic routing gap is worth understanding rather than working around blindly. HubSpot lets you associate a channel with a deal, and it lets a workflow send to a channel, but the workflow action does not read the association. So "notify the channel for this deal" needs either one workflow per channel, which does not scale past a handful, or a webhook into something that can look the association up and call Slack itself. n8n is the usual answer, and it is an hour of work.
Before any of that, decide what an alert is for. The pattern that survives contact with a sales team is one channel, a strict trigger, and a message that names the person who should act and what they should do. Every alert that does not meet that bar should go to a digest instead, because the cost of a noisy channel is not annoyance, it is that the useful alert arrives in a channel everyone stopped reading.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, Slack and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Not with the built-in workflow action. It sends to a channel picked at design time, and there is no option to send to the channel associated with the record that triggered the workflow even when that association exists. Teams solve it with one channel per segment, or by routing through n8n and calling the Slack API directly, which is about an hour of work.
Installing it and receiving notifications works on any HubSpot tier. Using a workflow to create a Slack channel automatically and associate it with a record requires Professional or Enterprise. Associating an existing channel by hand does not, which is the workaround lower down.
Events a named human must act on within minutes: a high-fit inbound lead, a reply, a deal gone quiet past a threshold you have agreed. Everything else belongs in a digest. The integration will happily post every activity type you tick, and a channel firing forty times a day gets muted.
Usually nobody turned them off. Somebody enabled every event type, the channel became noise, and the team muted it. That failure is silent and looks exactly like a working integration from the admin screen, which is why it is worth a ten-minute check each quarter.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.