Connect Slack to B6AI

Overview

The Slack integration brings B6AI into your team’s Slack workspace. It lets B6AI post into channels (handoff alerts, conversation notifications and system events) and lets your team act on customer conversations without leaving Slack.

It is ideal for keeping support and sales teams aware of what customers are asking, 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:

1. Post an alert to a Slack channel the instant a bot hands a conversation to a human.
2. Send notifications for new conversations, unassigned queues or SLA breaches.
3. Broadcast system alerts (integration failures, threshold breaches) to an ops channel.
4. Register slash commands (for example /b6ai status) so your team can query bots and conversations from Slack.
5. Reply to or claim a handed-off conversation directly from a Slack message action.

How the integration works

B6AI connects as a Slack app using OAuth 2.0. When you install the app, Slack issues a Bot User OAuth token (it starts with “xoxb-”) scoped to the permissions you approve.

B6AI uses that token to call Slack’s Web API for posting messages, and verifies inbound events and slash commands with your app’s Signing Secret. All calls are made server-side and the token is stored encrypted at rest.

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.

1. A Slack workspace where you can install apps, or a workspace admin who can approve app installs if your workspace restricts them.
2. Access to api.slack.com/apps to create a Slack app (any workspace member can create an app; installing it may need admin approval).
3. At least one channel B6AI can post to (public, or a private channel you will invite the app into).
4. The Enterprise Admin role in B6AI.

Create or prepare your Slack account

You will create a small Slack “app” that represents B6AI in your workspace. This is free and takes a couple of minutes.

1. If you do not already use Slack, create a workspace at slack.com/get-started.
2. Confirm whether your workspace allows members to install apps, or requires admin approval, if it requires approval, loop in a Workspace Admin now.
3. Decide which channel B6AI should post alerts to (for example #customer-support).

Choose a connection method

B6AI supports more than one way to connect Slack. Pick the one that fits your organization’s policies, the rest of this guide works for either.

Generate your Slack app credentials (Bot User OAuth token & Signing Secret)

B6AI authenticates with Slack using your Slack app credentials (Bot User OAuth token & Signing Secret). Follow these steps exactly, each field you copy here is entered into B6AI later.

1. Go to api.slack.com/apps and click Create New App → From scratch.
2. Name the app “B6AI” and select your workspace, then Create App.
3. Open OAuth & Permissions in the left menu, and under Bot Token Scopes add each scope listed in the next section.
4. Still on OAuth & Permissions, add the B6AI redirect URL (shown below) under Redirect URLs and Save.
5. Click Install to Workspace at the top of OAuth & Permissions and Allow, copy the Bot User OAuth Token (starts with xoxb-).
6. Open Basic Information and copy the Signing Secret (under App Credentials).

https://app.b6ai.ai/integrations/slack/callback

The B6AI redirect / callback URL

During credential setup, Slack asks for an authorized redirect (callback) URL. This is where Slack returns you after you approve access. Use the exact URL below, a mismatch is the most common cause of a failed connection.

https://app.b6ai.ai/integrations/slack/callback

Required permissions & scopes

Grant only the scopes below. Each one maps to a specific B6AI capability; requesting fewer reduces risk and speeds up any review your Slack administrator performs. The table explains exactly what each scope allows and why it is needed.

Finish configuration inside Slack

Complete these steps in the Slack console before connecting B6AI, so the credentials are fully active.

1. Confirm every scope above is added under Bot Token Scopes, then reinstall the app if Slack prompts you (scope changes require reinstalling).
2. If you want slash commands, open Slash Commands, create /b6ai, and set the Request URL to the value B6AI shows during connection.
3. Invite the B6AI app to any private channel you want it to post in with /invite @B6AI.

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.

1. In B6AI, open Settings → Integrations → Slack.
2. Choose your method: click Connect for OAuth, or switch to Manual and paste the Bot User OAuth Token and Signing Secret.
3. Select the default channel where handoff alerts and notifications should post.
4. Click Save: B6AI immediately posts a hidden test call to validate the token.

{
  "provider": "slack",
  "bot_token": "xoxb-…",
  "signing_secret": "…",
  "default_channel": "#customer-support"
}

Verify the connection

Confirm the integration is live before you rely on it in a bot.

1. Confirm the Slack card in B6AI shows a green “Connected” status.
2. Click Send test message and check that it appears in your default channel.
3. Trigger a handoff in a test conversation and confirm the alert posts to Slack.
4. If you enabled a slash command, run /b6ai in Slack to confirm it responds.

Troubleshooting

If the connection fails or an action does not work, match the symptom below to its cause and fix.

Limitations & rate limits

Keep these constraints in mind so your bots behave predictably at scale.

1. Slack’s Web API enforces tiered, per-method rate limits, very high posting volumes are paced by B6AI.
2. Rich formatting uses Slack Block Kit; extremely long messages are truncated by Slack.
3. Enterprise Grid workspaces may require org-admin approval before the app can be installed.

Security best practices

1. Grant only the scopes and permissions listed above, never request more “just in case”.
2. Rotate your Slack app credentials (Bot User OAuth token & Signing Secret) on a regular schedule, and immediately if you suspect exposure.
3. Restrict the Enterprise Admin role (which manages integrations) to a small, trusted group.
4. Prefer a dedicated service account or bot user over a personal login, so access survives staff changes.
5. Review the integration’s activity in the B6AI Activity Logs periodically for unexpected calls.
6. Disconnect the integration the moment a credential leaks; then rotate it in Slack before reconnecting.

Recommendations

1. Test against a sandbox or non-production Slack account before connecting live data.
2. Document which bots and flows depend on this integration so changes are predictable.
3. Set a recurring reminder to review scopes and rotate credentials.
4. Enable only the capabilities you actually use today; you can widen scopes later.