Slack

Connect a Slack workspace to ilert, then receive alerts, raise them, and look up who is on call from your channels.

With the integration for Slack you receive alerts in Slack channels and act on them there, raise new alerts from a channel, and check who is on call — without opening ilert.

Connecting a workspace is a one-time step by an Admin or Account owner. After that, each capability below is configured on its own, and anyone who may create alert actions can use the connection.

Connect your Slack workspace

Admin permission required

Only an Admin or an Account owner can connect a workspace. Other roles do not see Connectors in the sidebar.

1

Open the Connectors page

In the sidebar, go to Settings → Connectors. Under ChatOps, find the Slack card.

2

Connect

Click Connect. ilert forwards you to Slack, which lists the permissions the ilert app asks for. Pick the workspace and confirm.

3

Check the card

Slack returns you to the Connectors page. The Slack card now reads Connected and shows your workspace name underneath.

ilert shows no other confirmation, and a failed connection shows no message either — if the card still offers Connect, the connection did not happen. Start again, and see what can go wrong below.

4

Invite the bot to private channels

The ilert bot can post to any public channel without being a member. For a private channel, invite it first: mention @ilert in the channel and send the message, then click Add Them.

Invite the bot to public channels too if you want thread replies to become alert comments. Slack delivers message events only for channels an app has been added to, so posting alone does not give ilert the replies.

What ilert asks Slack for

Slack shows the permissions at the moment you connect. What ilert uses them for:

Permission	Used for
chat:write, chat:write.public	Posting alerts and updating them in place, including in public channels the bot has not joined
commands	The /il-alert, /il-oncall, and /il-help slash commands
users:read, users:read.email	Matching a Slack user to an ilert user by email address
channels:read, groups:read	Listing the channels you can pick in an alert action
channels:history, groups:history	Reading thread replies, which become alert comments — in channels the bot has been added to
channels:manage, groups:write	Creating an incident channel and inviting responders to it
team:read, pins:read, pins:write	Workspace details, and pinned messages in incident channels

Keep the connection working

Update the bot when ilert asks for new permissions

When a new ilert feature needs a permission your workspace has not granted, the Slack card replaces Connected with an Update button and a warning icon. Click it and confirm in Slack. Alerts keep flowing while you do.

Re-connect after changing something in Slack

On the Slack card, open the ⋯ menu and choose Re-connect. Use this after the app was removed in Slack, or when the bot stops responding.

The same menu has View alert actions using this connector, which lists every alert action that posts to this workspace, and Go to your workspace workspace, which opens Slack.

Disconnecting deletes your Slack alert actions.

⋯ → Disconnect removes the workspace connection and every Slack alert action in the account, immediately and without asking for confirmation. Alert actions that use a Slack webhook survive, because they do not use the connection. Alert sources keep working; they simply stop publishing to Slack. Recreate the alert actions after connecting again.

Select your use case

Post alerts to a Slack channel

Publish alerts to a channel and accept, reroute, and resolve them there.

Create alerts in Slack

Let people raise an alert from a channel with /il-alert, with or without an ilert account.

Look up who is on call

Answer "who do I page?" in the channel with /il-oncall.

Post alerts with a webhook

The fallback where you cannot install the ilert app: plain messages, no buttons.

What can go wrong

One workspace, one account. An ilert account can be connected to one Slack workspace, and a Slack workspace to one ilert account. Connecting a second one fails silently: you return to the Connectors page and the card is unchanged. Disconnect the existing pairing first.

The connection was canceled in Slack. Denying the permissions returns you to the Connectors page with the card unchanged, again without a message.

The app was removed in Slack. Alert actions remain in ilert but stop being delivered. Use Re-connect.

FAQ

Can I link multiple Slack workspaces to one ilert account?

No, only one Slack workspace can be linked to an ilert account.

Can multiple ilert accounts be linked to the same Slack workspace?

No, a Slack workspace can only be linked to one ilert account at a time.

Does everyone in Slack need an ilert account?

No. Anyone in a channel can accept and resolve the alerts posted there. Every other button, and the restricted mode of /il-alert and /il-oncall, needs an ilert user whose username or email address matches the email address on the Slack account.