Put incident response where your team already works
Connect one Slack channel to HowlOps for incident alerts and recovery notifications, then respond with signed message actions or /howlops commands.
A HowlOps account and permission to install apps in your Slack workspace are required. The install button opens the authenticated Integrations page before Slack’s approval screen.Slack is a response surface, not a second source of truth
Incidents, permissions, routing, and the audit timeline stay in HowlOps. Slack receives the context responders need and sends authenticated actions back to the same incident service.
Alert and recovery delivery
Send incident openings, updates, test alerts, and recoveries to the Slack channel selected during installation.
Signed incident actions
Acknowledge, silence, or resolve an incident from message actions. HowlOps verifies Slack’s signature, the linked installer identity, HowlOps permissions, and private-team visibility before changing state.
Slash commands
Use /howlops status, ack, silence, resolve, or help. Incident-mutating commands use the same authorization checks as the web application.
Optional incident war rooms
HowlOps can create a public channel for an organization-wide incident or a private channel for a private-team incident. Private channels initially invite the person who installed the connection.
The permissions HowlOps requests
HowlOps requests bot scopes only. It does not request message history, file access, admin scopes, or a Slack user token.
incoming-webhook
Post alerts to the channel chosen during installation.
commands
Register and receive the /howlops command.
channels:manage
Create a public incident war-room channel when that option is enabled.
groups:write
Create a private incident war-room channel for a private-team incident.
Clear boundaries for Slack data
HowlOps stores the Slack workspace and selected channel identifiers and names, the installer and bot user identifiers, the incoming webhook URL, and the bot access token. Provider credentials are encrypted at rest and masked in HowlOps API responses. Signed command and action payloads are processed to authorize and record incident activity.
If Slack reports that the app was uninstalled or its bot token was revoked, HowlOps disables every affected connection, removes its stored Slack credentials, and records the provider disconnect in the workspace audit trail. The channel record remains so routing references and historical evidence are not silently deleted. Reconnect Slack to issue new credentials.
You can also remove a connection from HowlOps at any time. For retention periods, legal bases, international transfers, deletion requests, and contact details, read the privacy policy.