Skip to main content
When a visitor is identified, Squid ID posts an alert to Slack with their name, company, role, and the page they’re on. Because it arrives in real time, you can reach out while they’re still on your site. By default every visitor goes to one channel. Squid ID can also send different visitors to different channels or people based on your ICPs, so each team only sees the visitors relevant to them.

​
If you’re coming from RB2B

If you currently use RB2B, here’s how the Slack integration compares:
RB2BSquid ID
DestinationsOne channelMultiple channels
Direct messagesNot availableSend to an individual teammate’s DM
RoutingAll visitors to the one channelPer-channel rules: all visitors, any ICP match, or specific ICPs
Multiple websitesShared streamEach channel fires only for its own website
Failure handlingNoneA broken channel is muted automatically without affecting the others

Why this matters. A single channel puts every visitor in one place, so your team sorts through them by hand. Routing by channel and direct message sends each visitor only to the people who need it, so a target account can go straight to the rep who owns it.

​
Before you start

You’ll move faster if these are already in place.
  • You’re an Owner or Admin on the website. Viewers can see alerts but can’t change routing.
  • The snippet is installed and verified, so there are visitors to route.
  • You can sign in to the Slack workspace you want alerts in.

​
Connect your Slack workspace

1

Open the Slack connector

Go to Settings → Connectors → Slack.
2

Sign in with Slack

Click Sign in with Slack. A Slack window opens.
3

Approve the permissions

Squid ID uses them to post messages, list your channels, and send direct messages.
4

Confirm it's connected

The window closes and your workspace shows as Connected. This is a one-time step per workspace.
You can also paste an Incoming Webhook URL instead of using sign-in. A webhook supports a single channel and does not support the channel picker or direct messages.

​
Create a channel route

A route is one destination plus a rule for what’s sent there. You can add as many as you need.
1

Add a channel

On the Slack page, click Add channel.
2

Name it

Enter a name, for example Sales · Enterprise.
3

Pick the destination

Choose a public channel, private channel, or a teammate’s direct message. Squid ID lists them from your connected workspace.
4

Choose what fires it

All visitors, any ICP match, or specific ICPs.
5

Save

The route is active immediately.

​
Common routing setups

Routes can be combined to send different visitors to different places. Some examples:
  • By deal size: Enterprise-ICP matches to a senior rep’s direct message, all other visitors to #sales.
  • By owner or territory: one route per rep, each filtered to the ICP for their accounts.
  • Executive alerts: a route to a founder’s direct message, filtered to a target-accounts ICP.
  • Catch-all: one “All visitors” route to a shared channel alongside your filtered routes.
  • Per website: each route only fires for the website it belongs to.
Routes can be added, edited, or removed at any time.

​
Send a test

Next to any route, click Test. Squid ID sends a sample alert through the same path a real visitor uses, so you can confirm the channel is reachable.

​
If a channel stops working

If a webhook breaks or a channel is deleted, Squid ID mutes that route after several failed sends (for ten minutes) so it doesn’t block other routes or repeatedly retry Slack. The muted route shows a warning with the last error, and resumes automatically once the destination is fixed.