
Belong CheckIn supports Slack Setup for teams connecting an AI agent through Belong AI Deploy. The capability is for Slack workspace owners and agent operators who want users to message the bot directly or mention it in a channel.
The setup connects a Slack app to the deployment. It covers creating the app, assigning bot token scopes, installing the app to a workspace, subscribing to bot events, and connecting the Bot User OAuth Token in the wizard. After deployment, the docs say to finish the documented channel checks.
Once connected, users can message the bot directly. In a channel, the bot must be invited and mentioned with its name. The bot can also reply in threads to keep conversations organized.
chat:write to send messages, app_mentions:read to respond when mentioned, im:history to read direct messages, and im:write to send direct messages. Add channels:history` only if the bot should read channel messages; the docs mark this scope as optional.xoxb-`.443 for webhook routes only. Other providers need a separate public HTTPS entrypoint in front of the deployment./webhook/slack/YOUR_DEPLOY_ID, on the public HTTPS webhook domain. Under Subscribe to bot events, add `message.im for direct messages and app_mention` for mentions.The permissions and event subscriptions serve different purposes. The OAuth scopes allow the bot to send or read the documented types of messages. The event subscriptions tell Slack to send the deployment direct message and mention events at the request URL.
Slack Setup is for teams that want to use a Belong AI Deploy agent in direct messages, channels, and threads. It fits when Slack is already the place where users are sending messages and the team wants the agent available there.
It is also for the person responsible for the deployment's public HTTPS entrypoint. DigitalOcean and Google Cloud have a documented path that opens public 443 for webhook routes only when Slack is selected. Other providers require a separate public HTTPS entrypoint.
The channel behavior is specific. For direct messages, users message the bot. For channels, staff invite the bot and mention it with `@botname`. Threads are available for organized replies.
The docs also list three optional presentation and command choices. Enable the Messages Tab in App Home so users can direct-message the bot. Add a description and profile picture under Basic Information. Use Slash Commands if you want to add custom /commands.
An event operations team uses Slack for day-to-day conversation. The team invites the deployed bot to a channel. When a team member needs the agent, they mention it by name. The bot replies in a thread, so the response stays with the conversation that prompted it. For a private exchange, a team member can message the bot directly.
This scenario uses only the documented Slack behaviors: direct messages, channel mentions, and threaded replies. What the agent can answer or do depends on the agent that was deployed, not on the Slack channel connection itself.
Follow the Slack Setup guide to create the app, assign the required scopes, configure the request URL, and connect the Bot User OAuth Token in the wizard. Open Belong CheckIn to reach the Belong experience used for setup.
Before testing, check that the Bot User OAuth Token has been pasted, that `message.im and app_mention` are subscribed, and that the public HTTPS request URL is available. After deployment, complete the documented channel checks.
The docs list `chat:write, app_mentions:read, im:history, and im:write. channels:history` is optional for reading channel messages.
Subscribe to `message.im for direct messages and app_mention` for mentions. Send them to the deployment's documented webhook request URL.
Users can message the bot directly. In a channel, invite the bot and mention it with `@botname`. The bot can reply in threads to keep conversations organized.