1. Add to Slack
Under Account settings > Integrations, press Add to Slack and approve the request on Slack's own consent screen. The app asks for two scopes: commands (to receive /realuptime) and chat:write (so it can post as itself once it is used as a notification channel). Nothing else.
2. Run a command
/realuptime status shows every monitor's state; /realuptime status <name> filters to monitors whose name matches; /realuptime incidents lists open incidents; /realuptime help lists all three. Every answer is private to the person who ran the command, never posted to the channel.
3. /isdown is free and needs no account
Once the app is in a workspace, anyone can run /isdown <service> or /realuptime isdown <service> (for example /isdown openai or /realuptime isdown stripe) to ask whether a third-party service is down, answered from the same probe readings the public outage pages show, with a link to the full reading. Unlike /realuptime status, this does not require the workspace to be connected to a realuptime account. See the /isdown how-to for the Discord equivalent.
4. One workspace, one account
Each Slack workspace connects to exactly one realuptime account, the one that was signed in when Add to Slack was pressed. Reinstalling (pressing Add to Slack again after removing the app) replaces the stored credential; it does not create a second connection.
5. Remove it
Either press Remove under Account settings > Integrations, or remove the app from Slack's own App Directory. Either way, realuptime stops answering commands for that workspace immediately, and the removal is recorded in the account audit log.
Go deeper
The full reference lives in the docs: API documentation. Error codes named above are each explained in the error-code reference.