Set Up the statusas Slack Agent

A step-by-step tutorial to install the statusas Slack agent and manage incidents directly from Slack


Time	~5 minutes
Level	Beginner
Prerequisites	statusas account on a paid plan (the Slack agent is not available on Hobby), Slack workspace where you have permission to install apps

In this guide, you'll install the statusas Slack agent so you can manage incidents directly from your Slack workspace — no need to switch to the dashboard. The agent uses an LLM to interpret natural-language messages like "create an incident for the payment API" and turn them into status page actions.

Caution

The Slack agent is AI-powered. It interprets your messages with an LLM, so its responses and actions may occasionally be incorrect, incomplete, or unexpected. Always review the bot's output — especially before publishing incident updates, resolving incidents, or scheduling maintenance — and confirm the change in your statusas dashboard.

Install the Slack agent

1. Go to settings

Navigate to Settings > Integrations in your statusas dashboard.

2. Install the Slack integration

Click the Add to Slack button. You'll be redirected to Slack's authorization page where you can select the workspace you want to connect. (If you see an Upgrade button instead, your plan doesn't include the Slack agent.)

Grant the requested permissions and click Allow to complete the installation.

Note

Make sure you select the correct Slack workspace if you belong to multiple workspaces.

3. Add the bot to a channel

Installing the app doesn't pick a channel — no channel is selected during the OAuth flow. Invite the bot to the channel you want to use, either by running the subscribe command there:

/statusas subscribe https://acme.statusas.lt

which subscribes the channel to a status page and joins the bot at the same time, or by /invite @statusas for a private channel the bot can't self-join.

The available slash commands are:

/statusas subscribe <status-page-url> — subscribe this channel to a status page
/statusas unsubscribe [status-page-url] — unsubscribe. The URL is optional when the channel is subscribed to exactly one page; with several, the command lists them and asks you to name one.
/statusas subscriptions — show this channel's subscriptions
/statusas help — show this list (also the response to any unrecognised subcommand)

4. Verify the installation

In that channel, type:

@statusas what's the status of my monitors?

The bot should respond with a summary of your monitors. If you see a response, the installation is working.

Tip

The bot only responds when mentioned with @statusas — it won't interrupt your conversations.

5. Start managing incidents from Slack

Here are some examples of what you can do:

Create an incident

Notify your subscribers about a new issue.

@statusas create an incident for the payment API – high latency detected.

Update an incident

Keep your status page updated while you investigate.

@statusas keep the status page updated that we are still monitoring the issue.

Resolve an incident

Close an active incident and let your subscribers know.

@statusas resolve the ongoing incident on my API status page.

Schedule maintenance

Plan downtime so subscribers are informed in advance.

@statusas schedule a maintenance window for my database next Friday from 2–3 PM.

What you've accomplished

Installed the statusas Slack agent in your workspace
Connected your statusas account to Slack
Learned how to manage incidents directly from Slack

Troubleshooting

The bot doesn't respond when mentioned

Check the channel — make sure the bot has been added to it. Run /statusas subscriptions there, or re-run /statusas subscribe <status-page-url> to join it. Private channels can't be self-joined; use /invite @statusas.
Check permissions — go to Settings > Integrations and verify the Slack integration shows as connected.
Reinstall — if the integration appears disconnected, click Add to Slack again to re-authorise.

Create a status page — share your service status publicly with users.
Create a monitor — set up uptime monitoring for your endpoints.