Connect
Add the bot
Install the Nuphos Slack app to your workspace and invite the bot into the channels where you want to use it.Map channels and users
In Settings → Workspace → Slack, create mappings: Channel mapping — connects a Slack channel to your Nuphos team:
User mapping — links a Slack user to a Nuphos team member:
You can find these IDs in Slack’s channel/user details. Users are auto-linked by
email on first interaction; manual mappings override that.
In the Nuphos app
Slack conversations are real agent sessions — each one shows up in the team’s workspace with its full transcript, so anyone in the app can see what the agent was asked in Slack and what it did. Mappings are managed in Settings → Workspace → Slack.What the agent can do for you
Everything it can do in the app, from where your team already talks:- Mention the bot with a question — “@nuphos why is checkout slow?” — and it investigates across your connectors and replies in the channel.
- During an incident, the whole channel sees the same investigation unfold — either as a live-updating status message or a threaded reply. See Chat with the agent.
- Changes proposed from Slack still arrive as plans to approve — handy for a quick “yes, do it” while on the go.
Permissions & authorization
Slack is an entry point, not an escape hatch — the same boundaries apply as in the app:- Hard boundary — who is acting. The user mapping decides which Nuphos user a Slack message acts as, and that user’s access control applies: their role, the member allow-lists on each account, and the credentials selected for the session. Someone who can’t use the production account in the app can’t reach it from Slack either.
- Soft boundary — what may run. Changes still require plan approval, and Auto-authorization still governs each command — your standing rules apply identically to sessions started from Slack.
Good to know
- Only mapped channels work — the bot ignores channels that aren’t mapped to a team, so adding it to a channel isn’t by itself an access grant.
- Auto-linking by email means most users never need a manual mapping; use manual mappings when Slack and Nuphos emails differ.