Skip to main content
When a visitor is identified, Squid ID posts a message to Microsoft Teams with their name, company, role, and the page they’re on. Like the Slack router, Teams is multi-destination and per-website: you can send different visitors to different channels or people based on which ICP they match. You can connect Teams two ways:
  • Sign in with Microsoft and pick channels from a list.
  • Paste a webhook URL from a Teams Workflows flow (no app install or admin approval needed).
These channels apply to the website you have selected. Switch sites to set up Teams for another website.

​
If you’re coming from RB2B

RB2BSquid ID
ConnectSign in with MicrosoftSign in with Microsoft, or paste a Workflows webhook URL
DestinationsOne team and channelMultiple channels per website
RoutingGeneric filters (company-only, repeat visitors, daily recap)Per channel: all visitors, any ICP match, specific ICPs, or any high-intent page hit
Contact dataVisitor profileName, company, role, and page, plus mobile, personal email, and address when Squid ID+ is set to Automatic
RequirementsMicrosoft 365 business and admin approval; free Teams not supportedSame for sign-in, or use the webhook option with no app install
Pause without disconnectingNot availablePer-channel toggle

Why this matters. Send the right visitors to the right Teams channel instead of one firehose, and get a fuller contact record on each match.

​
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 the connector but can’t change it.
  • The snippet is installed and verified, so there are visitors to route.
  • For sign-in: a Microsoft 365 business account that can authorize an app. For the webhook option: the ability to add a Workflows flow to a channel.

​
Connect Microsoft Teams

1

Open the Teams connector

Go to Settings → Connectors and click Connect on the Microsoft Teams card.
2

Choose how to connect

Pick Sign in with Microsoft to authorize once and select channels from a list, or Paste a webhook URL if you’d rather not install an app.
3

Add the webhook (webhook option)

In Teams, open the channel, then Workflows → Post to a channel when a webhook request is received. Copy the URL it gives you and paste it into Squid ID.
4

Add a destination and a rule

Name the destination, pick a channel or a person, and choose what routes to it: all identified visitors, any ICP match, specific ICPs, or any high-intent page hit. Add as many destinations as you need.
Squid ID checks that a pasted URL is a Teams webhook (a webhook.office.com or logic.azure.com address). A URL in any other format is rejected.

​
Channels and routing

Each channel has its own routing rule, so a single website can feed several channels with different filters:
  • All identified visitors posts every match.
  • Any ICP match posts only visitors that match at least one of your ICPs.
  • Only specific ICPs posts visitors that match the ICPs you pick.
  • Any high-intent page hit posts only visitors who viewed a page you flagged as high intent, like pricing or a demo. The card names the exact page.
Use Test on a destination to send a sample message and confirm it lands.
When Squid ID+ is set to Automatic, the Teams message also includes the unlocked fields for that visitor, such as mobile phone, personal email, and mailing address.

​
Route to a person (direct message)

When you sign in with Microsoft, the picker lists both channels and people in your organization. Pick a person to send their visitor alerts as a Teams direct message instead of into a channel.
You can’t direct-message the account you connected with. Teams sends the message from the connected account, and a direct message needs two different people. The connected account still appears in the People list, but it’s greyed out and labeled so you know why.

​
Send alerts to yourself

To receive your own direct messages, connect with a dedicated service account instead of your personal one. The alert is then delivered from the service account to you, and you become selectable in the People list. One service account can message everyone on your team, so it’s also the cleanest setup when several teammates each want their own direct messages.
1

Create the service account

In the Microsoft 365 admin center, go to Users → Active users → Add a user. Give it a clear name like Squid Notifications (for example squid-notifications@yourcompany.com) and set a password.
2

Assign a Teams license

Assign a license that includes Microsoft Teams, the same kind your team uses. The account has to be a licensed Teams user to send chats. This adds one license seat.
3

Reconnect Squid ID with it

In Settings → Connectors → Microsoft Teams, click Disconnect, then Connect again. At the Microsoft account picker, sign in as the service account.
4

Add people as destinations

Open Add destination → Pick a channel or person. Your real teammates (including you) now appear as selectable People. Add yourself, and the alerts arrive as a direct message from Squid Notifications.
The destination must be a licensed Teams user, not a shared mailbox or a group. Direct messages and channel delivery both depend on the connected account’s Microsoft 365 plan allowing the Teams chat API. If People is empty or channels fail to load, your tenant may be on a plan that limits it.

​
Pause or disconnect

  • Pause: Toggle a destination off to stop its alerts without removing it. Flip it back on to resume.
  • Disconnect: Remove an individual destination, or disconnect Microsoft to drop the sign-in and all of its destinations at once.

​
Multiple websites

Teams channels are scoped to the website you have selected. If your account owns more than one website, switch the active site and set up the channels you want for each.