Connect Slack to B6AI
Set up the Slack integration end to end, from creating credentials in Slack to verifying the live connection and using it in your bots.
Overview
The Slack integration brings B6AI into your team’s Slack workspace. It lets B6AI post into a channel (handoff alerts, conversation notifications and system events) so your team sees what customers are asking.
It is ideal for keeping support and sales teams aware of activity, and for surfacing the moment a bot escalates a conversation to a human.
What you can do with Slack
Once connected, your bots and agents can use Slack inside conversations and automations. Typical uses include:
- Post an alert to a Slack channel the instant a bot hands a conversation to a human.
- Send notifications for new conversations, unassigned queues or SLA breaches.
- Broadcast system alerts (integration failures, threshold breaches) to an ops channel.
How the integration works
B6AI posts to Slack using an Incoming Webhook URL you generate in your workspace. The webhook is bound to one channel you pick when you create it.
B6AI sends messages to that URL server-side; the URL is stored encrypted at rest. No bot user, OAuth token or signing secret is needed for this flow.
Prerequisites
Make sure all of the following are in place before you start. Each one is required, skipping any will cause the connection to fail later.
- A Slack workspace where you can add an Incoming Webhook (or a workspace admin who can).
- The channel you want B6AI to post to (public, or a private channel you can add the webhook to).
- The Enterprise Admin role in B6AI.
Create or prepare your Slack account
You will create a free Slack “app” only to generate an Incoming Webhook — a couple of minutes, no code.
- If you do not already use Slack, create a workspace at slack.com/get-started.
- Confirm whether your workspace lets members add apps/webhooks, or requires admin approval.
- Decide which channel B6AI should post to (for example #customer-support).
Generate your Slack Incoming Webhook URL
B6AI authenticates with Slack using your Slack Incoming Webhook URL. Follow these steps exactly, each field you copy here is entered into B6AI later.
- Go to api.slack.com/apps and click Create New App → From scratch; name it “B6AI” and pick your workspace.
- In the left menu open Incoming Webhooks and toggle Activate Incoming Webhooks on.
- Click Add New Webhook to Workspace, choose the channel B6AI should post to, and Allow.
- Copy the generated Webhook URL — it looks like https://hooks.slack.com/services/T…/B…/…
Connect Slack in B6AI
Now enter your credentials in B6AI. Signed in as an Enterprise Admin, open Settings → Integrations, find the Slack card and click Connect, then complete the form. Every field is explained below.
- In B6AI, open Settings → Integrations and click Configure on the Slack card.
- Paste the Incoming Webhook URL.
- Click Save — B6AI sends a hidden test to validate the webhook.
{
"provider": "slack",
"webhook_url": "https://hooks.slack.com/services/T…/B…/…"
}| Field | What it is | Example value |
|---|---|---|
| Webhook URL | The Slack Incoming Webhook that posts to your chosen channel | https://hooks.slack.com/services/T…/B…/… |
Verify the connection
Confirm the integration is live before you rely on it in a bot.
- Confirm the Slack card in B6AI shows a green “Connected” status.
- Click Send test message and check it appears in the webhook’s channel.
- Trigger a handoff in a test conversation and confirm the alert posts to Slack.
Troubleshooting
If the connection fails or an action does not work, match the symptom below to its cause and fix.
| Symptom / error | Likely cause | How to fix it |
|---|---|---|
| no_service / 404 | The webhook was deleted or the app was removed from the workspace | Recreate the Incoming Webhook and paste the new URL |
| channel_not_found / channel archived | The webhook’s channel was archived or deleted | Create a new Incoming Webhook for an active channel |
| invalid_payload | The URL was truncated when copied | Re-copy the full Webhook URL (all path segments after /services/) |
| Nothing posts, no error | Wrong workspace or a stale URL | Regenerate the webhook and reconnect in B6AI |
Limitations & rate limits
Keep these constraints in mind so your bots behave predictably at scale.
- An Incoming Webhook posts to the single channel it was created for — use one webhook per channel.
- Rich formatting uses Slack Block Kit; extremely long messages are truncated by Slack.
- Two-way actions (claim/reply from Slack, slash commands) require an advanced bot-token setup and are not part of the webhook flow.
Security best practices
- Grant only the scopes and permissions listed above, never request more “just in case”.
- Rotate your Slack Incoming Webhook URL on a regular schedule, and immediately if you suspect exposure.
- Restrict the Enterprise Admin role (which manages integrations) to a small, trusted group.
- Prefer a dedicated service account or bot user over a personal login, so access survives staff changes.
- Review the integration’s activity in the B6AI Activity Logs periodically for unexpected calls.
- Disconnect the integration the moment a credential leaks; then rotate it in Slack before reconnecting.
Recommendations
- Test against a sandbox or non-production Slack account before connecting live data.
- Document which bots and flows depend on this integration so changes are predictable.
- Set a recurring reminder to review scopes and rotate credentials.
- Enable only the capabilities you actually use today; you can widen scopes later.