HubSpot workflows are a reasonable place to start when you want to get CRM activity into Slack. For simple, high-signal triggers, they do the job. The trouble is that you can get pretty deep into designing one before you realise it has a critical limitation.
This isn’t a reason to avoid them. It’s a reason to know what you’re getting into.
Where they work well
If you haven’t used them before, the short version is: inside any HubSpot workflow, you can add a “send a Slack notification” step that fires a message to a channel or a user when the trigger conditions are met. That is the whole mechanism.
The sweet spot is a single clear trigger with a single clear action. These work because the logic is simple, the recipient is obvious, and the message has a natural next step. Good examples:
- A new inbound lead that needs a fast response
- A deal moving to a key pipeline stage
- A high-value form submission
- A deal marked closed-won, so the success team knows to spin up their onboarding process or create a task in their own pipeline before the rep has even sent the handoff email
HubSpot lets you add action buttons to the notification, so someone can log a note or create a task without leaving Slack. For straightforward alerts like these, that’s genuinely useful.
Where they fall apart
Where did that message come from? Once you have a few workflows sending Slack notifications, tracing which workflow generated which message becomes harder than it should be. There is no sender label, no easy audit trail. If something is firing that should not be, finding the culprit takes longer than you would like.
Who set all these up? Without a naming convention agreed on from the start, a list of Slack notification workflows quickly turns into an archaeological dig. Months later, nobody can tell which ones are still needed, which ones overlap, and which ones were built by someone who’s since left.
Why does this look so basic? The messages themselves are fairly constrained. You can pull in properties and add buttons, but if you want something that reads well in a channel and gives people the right context at a glance, you’ll hit the ceiling of what the tool allows.
Can I schedule this for Monday morning? Sort of. Timing options are limited, and anything involving a rolling time window gets complicated fast.
Can it go to different channels depending on the deal? Not natively. The workflow action sends to a fixed, pre-selected Slack channel. Routing based on deal owner, region, or team means branching logic that gets unwieldy quickly, or bringing in a third-party tool.
Wait, the date picker doesn’t do quarters? This one catches people out. If you want to build something like “alert me when a deal with a close date this quarter has its close date pushed to next quarter,” the date triggers don’t support rolling quarters. The whole workflow falls apart at the first step.
What this means in practice
Sending Slack notifications as part of a HubSpot workflow is a handy thing to know about. But the feature has its limits, and they tend to appear at the exact moment you’re trying to build something slightly more specific than the tool was designed for.
Knowing that before you start saves you from building something you will have to unpick later.