Slack Integration — ZopNight Alerts Where Your Team Already Works
What does the Slack integration do?
Slack delivers ZopNight events as Block Kit cards with a button that opens the related alert, service, export or review page in ZopNight. Setup needs 2 bot scopes and 3 values: token, channel ID and signing secret. Each channel gets its own subscription matrix scoped to accounts, resource groups or teams.
Connect Slack once and every ZopNight event your team cares about lands in the channel of your choice as a rich, readable card: resources stopped and started, budgets crossing thresholds, cost anomalies, remediation approvals, report exports. Cards include a button that opens the related alert, service, export or review page in ZopNight.
Two bot scopes, cards, and live credential checks
ZopNight uses a Slack app you create in your workspace with two bot scopes (chat:write and chat:write.public). Messages are delivered as Block Kit cards with a title, facts, severity and a deep link back to ZopNight. Every channel gets a per-channel subscription matrix: pick exactly which event types it receives, scoped org-wide or to specific cloud accounts, resource groups, resources or teams. Credentials are verified live at setup (auth.test plus a channel lookup) so misconfigurations surface immediately, and a test-send button confirms end-to-end delivery.
Six steps from a new Slack app to a test message
- Create a Slack app (api.slack.com/apps > Create New App > From scratch).
- Under OAuth & Permissions, add bot scopes chat:write and chat:write.public, then Install to Workspace.
- Copy the Bot User OAuth Token (starts xoxb-).
- Right-click your target channel > View channel details > copy the Channel ID.
- From Basic Information > App Credentials, copy the Signing Secret.
- In ZopNight: Settings > Notifications > Add Channel > Slack; paste all three values and send a test notification.
Deep-link buttons and per-event subscriptions
All ZopNight event families with per-event, per-scope subscriptions. Severity-aware formatting (info, warning, critical). Buttons that open the related alert, service, export or review page in ZopNight. Recommendation sharing to any Slack channel. Live credential validation and test sends.
Limits worth knowing before you connect
Bot token, channel ID and signing secret are all required. The bot must be able to post to the channel (chat:write.public covers public channels; invite the bot for private ones).
Slack integration: common questions
What Slack scopes does ZopNight need?
Two bot scopes: chat:write and chat:write.public. The second covers public channels. For a private channel, invite the bot to it.
Which values do I paste into ZopNight?
Three. The Bot User OAuth Token, which starts xoxb-, the target channel ID from View channel details, and the Signing Secret from Basic Information. All three are required, and ZopNight verifies them live with auth.test plus a channel lookup when you save.
Can an engineer act on an alert without leaving Slack?
Not inside Slack itself. Each card carries a button that opens the related alert, service, export or review page in ZopNight, so the on-call engineer is one click from where the action happens. The buttons are links, not in-Slack actions.