Slack integration · Team alerts
Know the moment a chat needs you.
SuperBot connects to Slack through an incoming webhook for one channel. Each selected event posts a short message to that channel — the event name plus the visitor's name, email, company, and message when known — so your team sees new leads and escalations without watching the inbox.
- Incoming webhook URL
- SuperBot → one Slack channel (messages, write)
- Free, Starter & Pro
How the Slack integration works
An incoming webhook can only post into the channel it was created for. SuperBot cannot read messages, list channels, or see members, which keeps the Slack side of the connection as narrow as it gets.
The alert that matters most is “Conversation escalated to a human”: a visitor asked for a person, and the Slack message gets someone into the SuperBot inbox quickly. Add more connections if you want different events in different channels.
- New lead captured
- Form submitted
- New conversation started
- Conversation escalated to a human
Highlighted: the events most teams keep for this connector. You choose per connection.
What gets sent
| From SuperBot | In Slack |
|---|---|
| Event | Bold title, e.g. “Conversation escalated to a human” |
| Name | • Name line |
| • Email line | |
| Company | • Company line |
| Message | Final line |
Connect Slack to SuperBot
- In Slack, add the Incoming Webhooks app (Slack → Apps → Incoming Webhooks), choose a channel, and copy the webhook URL. It starts with https://hooks.slack.com/services/.
- In SuperBot, open Dashboard → Integrations, find Slack, and select Connect.
- Paste the URL into “Incoming webhook URL”.
- Under “Send these events”, keep only the events you want this connection to receive. All four are ticked by default: new lead captured, form submitted, new conversation started, and conversation escalated to a human.
- Select “Connect & verify”. SuperBot posts “SuperBot is connected to this channel.” so you can see it working straight away.
- Use “Send test” any time to post a sample lead alert.
Don't have a workspace yet? Sign up free — no card needed — then open Dashboard → Integrations.
Permissions and privacy
- The webhook URL is treated as a secret: encrypted before storage and never shown back in full.
- SuperBot only accepts hooks.slack.com webhook URLs, so alerts cannot be pointed at another host by mistake.
- Messages include the visitor's name, email, company, and message when known. Choose a private channel if that should not be visible to your whole workspace.
- Remove the webhook in Slack, or Disconnect in SuperBot, to stop alerts.
What teams use Slack with SuperBot for
- Fast human handoff
A visitor asks for a person; the channel lights up and a teammate joins the conversation from the SuperBot inbox.
- A live lead feed for sales
Post “New lead captured” into #sales so every captured email is visible the moment it arrives.
- Separate channels per team
Use one connection per channel with its own events — escalations for support, leads for sales.
FAQ
Slack integration questions, answered.
Ready to try it? Start free or compare plans. Every integration is on every plan.
Can SuperBot read my Slack messages?
No. An incoming webhook can only post into the one channel it was created for. SuperBot cannot read, list, or search anything in Slack.
Can I reply to visitors from Slack?
No. Slack gets an alert; replies happen in the SuperBot inbox, where the full conversation is.
Can alerts go to more than one channel?
Yes. Add Slack again with a second webhook URL and pick different events for it.
What does the Slack message contain?
The event name, then the visitor's name, email, company, and message on separate lines when SuperBot has them.
Is the Slack integration free?
Yes. It works on every SuperBot plan, including Free.