Setup
1
Create the app
At api.slack.com/apps, create a new app from
scratch in your workspace.
2
Add bot scopes and install
Under OAuth & Permissions, add the bot token scopes your use needs, then
install the app to the workspace. Copy the Bot User OAuth Token — it
starts with
xoxb-.3
Enable Socket Mode
Under Socket Mode, turn it on. Create an app-level token with the
connections:write scope and copy it — it starts with xapp-.4
Enable Event Subscriptions
Under Event Subscriptions, turn it on and subscribe to the bot events
you want (for example
message.im and message.channels). Leave the
Request URL blank — Socket Mode is what delivers these events, and a
Request URL is neither required nor read.5
Configure the channel
In the Portal: Agents → (agent) → Channels → Slack → Set up. Two fields:
- Bot token (xoxb-…) — the OAuth bot token
- App-level token (xapp-…) — needs
connections:write, used for Socket Mode
6
Enable it
Flip the enable switch. Noorle opens the Socket Mode connection at that
point.
7
Confirm
Use Test connection on the channel row. It reports back as
“Connected as @”.
Scopes
Which bot scopes you need depends on where the bot should work — DMs, public channels, private channels — and Slack, not Noorle, enforces them. Noorle callschat.postMessage to reply, auth.test for the connection test, and Socket
Mode’s connection endpoint.
Nothing in Noorle validates or requests scopes, so grant what your Slack app
configuration actually needs and no more.
Rotating tokens
Paste the new token, save, then re-enable the channel. Changing a credential force-disables it.Limits
Cost
Slack messages are free. The agent’s model and tool usage bills normally.Autonomy
Linking users
Link a member’s Slack Member ID (U01ABC23DEF) under Settings → Users →
(user) → Linked Platforms. Slack links immediately — no verification step.
Troubleshooting
Removing the channel stops the Socket Mode connection. There is no webhook to
unregister.