Workflow webhook triggers are 10 a minute, which is the real ceiling on enrich on demand.
- Moves: Messages, Contacts, Companies
- Needs: A Reverse Contact API key, somewhere to run the lookup, and a Slack app or an incoming webhook
Ten integrations, nine of them cheap and quick, and all ten capable of being configured into uselessness inside a week. The constraint here is never the connection.
The last step of almost every working sales stack.
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 these the highest-leverage cheap integrations in the directory and the ones teams configure worst.
The technical limit worth knowing is HubSpot's. A workflow can send a Slack message, and a deal or company record can be associated with a Slack channel, but the workflow action does not read that association. There is no built-in option to notify the channel attached to the deal that triggered the workflow. The workarounds are one workflow per channel, which does not scale, or a webhook into something that can look the association up and call Slack itself.
Everything else here is a volume problem rather than a feature problem. Nine of these ten will happily post every event type they support, and a channel that fires forty times a day gets muted. A muted channel is worse than no integration, because everybody still believes the alerting works.
The exception is the one with no app behind it. Reverse Contact publishes nothing on the Slack Marketplace, and Slack documents no Workflow Builder step that calls an arbitrary URL, so that page is a lookup that runs somewhere else and posts an answer back. It fires when something asks it to rather than on every event, which makes it the only page on this hub where the volume is yours to choose and the ceiling is a published figure: workflow webhook triggers are 10 a minute.
Slack sits in the collaboration layer, with 2 other tools in this directory. Counted across the whole directory it reaches 10 of the other 22 tools, and the integration matrix shows that row against every other.
Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.
Whichever of these you connect, the integration moves the record. We fill it.
Start for freeWorkflow webhook triggers are 10 a minute, which is the real ceiling on enrich on demand.
Notifications are easy. Routing to the right channel is the part nobody built.
The one pair where the same company owns both sides.
Channel alerts come from streams, and a stream has to be the standard kind.
Free on every plan, and only the person who set it up can extend it.
Connected once for the whole instance, then every notification is personal.
One message a second per channel, and a bot message cannot start a Zap.
The trigger needs a bot token and the node wants OAuth, so you build both.
An admin installs it once, then every person has to connect their own account.
Not an alert feed any more: you prospect, enrich and sequence by typing in Slack.
4 things that decide whether a Slack integration will work for you, in the order they usually bite.
An alert that does not name who should act and what they should do is a notification. The version of this that still works in three months routes a strict trigger to a channel someone is accountable for.
The subtractive configuration is the right one. Route the events a human must act on within minutes. Everything else belongs in a report nobody has to read in real time.
Creating a Slack channel from a HubSpot workflow needs Professional or Enterprise. Associating an existing channel by hand does not, which is the workaround lower down.
If you need per-record channel routing, budget an hour in n8n rather than looking for the setting. It is not there, and it is the most requested thing on this pair.
Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.
Workflow webhook triggers are 10 a minute, which is the real ceiling on enrich on demand.
One way, in → 02Notifications are easy. Routing to the right channel is the part nobody built.
Events only → 03The one pair where the same company owns both sides.
Events only → 04Channel alerts come from streams, and a stream has to be the standard kind.
Events only → 05Free on every plan, and only the person who set it up can extend it.
Two-way sync → 06Connected once for the whole instance, then every notification is personal.
Events only → 07One message a second per channel, and a bot message cannot start a Zap.
Events only → 08The trigger needs a bot token and the node wants OAuth, so you build both.
Two-way sync → 09An admin installs it once, then every person has to connect their own account.
Two-way sync → 10Not an alert feed any more: you prospect, enrich and sequence by typing in Slack.
Two-way sync →The hub most sales stacks are actually built around.
See the 17 integrations →The widest integration surface, gated by edition.
See the 12 integrations →A CRM with a data model you write yourself.
See the 3 integrations →People and company data for every tool in this directory.
See the 22 integrations →Deep native CRM integrations, sold by tier.
See the 3 integrations →An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.
Free trial, no card required, and 500 credits to start.
The questions that come up before anyone opens a setup guide.
Not with the built-in workflow action. The action sends to a channel selected 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.
To install it and receive notifications, no. To have a workflow create a Slack channel and associate it with a record automatically, you need Professional or Enterprise.
Usually nobody turned it off. Somebody enabled every event type, the channel became noise, and the team muted it. That failure is silent and it looks exactly like a working integration from the admin screen.
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.