Slack integrations

Slack integrations, and the routing nobody built

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.

slack.com 10 integrations
layerCollaboration
entry$0/mo
authOAuth 2.0, app-level tokens for ...
automationWorkflow Builder, plus events an...
verified2026-09-18
checked Guides written 10 of 10
10integrations checked
7built natively
4sync both ways
4need a plan upgrade
The short version

What decides a Slack integration

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.

All 10

Every Slack integration, with what it moves

Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 10 of 10
⋅

Slack and HubSpot

Events only
BuiltNativeMarketplace app
WatchNeeds a higher plan

Notifications are easy. Routing to the right channel is the part nobody built.

  • Moves: Activities, Messages, Deals, Companies
  • Needs: HubSpot Professional or Enterprise to create a channel from a workflow
Needs a higher plan · minutes Read the guide
⋅

Slack and Salesforce

Events only
BuiltNativeMarketplace app
WatchNeeds a higher plan

The one pair where the same company owns both sides.

  • Moves: Deals, Activities, Messages, Contacts
  • Needs: Sales Cloud, plus a Slack workspace you can install apps into
Needs a higher plan · minutes Read the guide
⋅

Slack and Gong

Events only
BuiltNativeMarketplace app
WatchPaid licence first

Channel alerts come from streams, and a stream has to be the standard kind.

  • Moves: Messages, Activities
  • Needs: A Gong contract, a Slack admin to install the app, and a Gong admin to connect it
Paid add-on or licence · minutes Read the guide
⋅

Slack and Outreach

Events only
BuiltNativeMarketplace app
WatchPaid licence first

Connected once for the whole instance, then every notification is personal.

  • Moves: Messages, Activities
  • Needs: An Outreach contract, an Outreach admin, and permission to add apps to Slack
Paid add-on or licence · minutes Read the guide
⋅

Slack and Zapier

Events only
BuiltZapier, Make or n8nMarketplace app

One message a second per channel, and a bot message cannot start a Zap.

  • Moves: Messages
  • Needs: A Zapier plan sized to your task volume, and a free app slot on a free Slack plan
Metered by usage · minutes Read the guide
↔

Slack and n8n

Two-way sync
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

The trigger needs a bot token and the node wants OAuth, so you build both.

  • Moves: Messages
  • Needs: An n8n instance you host or rent, and a Slack app with the right token type
Metered by usage · hours Read the guide
↔

Slack and Google

Two-way sync
BuiltNativeMarketplace app
WatchNo upgrade needed

An admin installs it once, then every person has to connect their own account.

  • Moves: Messages, Activities
  • Needs: Nothing to buy. An admin installs each app, then every member connects their own account.
Included on both sides · minutes Read the guide
↔

Slack and Apollo

Two-way sync
BuiltNativeMarketplace appBuilt on the API
WatchNo upgrade needed

Not an alert feed any more: you prospect, enrich and sequence by typing in Slack.

  • Moves: Messages, Activities, Contacts
  • Needs: An Apollo plan and a Slack workspace. An Apollo admin to connect it, and professional or organization for agents.
Included on both sides · minutes Read the guide
Buyer's guide

How to pick, and what to check first

4 things that decide whether a Slack integration will work for you, in the order they usually bite.

01

One trigger, one channel, one named owner

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.

02

Replies and bookings, not opens and clicks

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.

03

Check what your tier allows

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.

04

Dynamic routing is a build, not a setting

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.

Written up

The Slack integrations with a full guide

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.

Other tools

Integrations for the rest of the stack

Connecting Slack is half the job

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.

FAQ

Slack integrations, asked and answered

The questions that come up before anyone opens a setup guide.

Can HubSpot notify the Slack channel associated with a deal?

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.

Do I need a paid HubSpot plan for the Slack integration?

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.

Why did our Slack alerting stop working?

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.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit behind the 10 integrations on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-09-18
Sources
6 vendor documents
Paid placement
None

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.

Ask an assistant