SolidPing for Slack
Monitor your services and respond to incidents directly from your Slack workspace. Get alerts, create checks with a slash command, acknowledge incidents, and sign in to the SolidPing dashboard with your Slack identity.
What it does
- Incident alerts in any channel — every check failure, escalation, and recovery, posted where your team already works.
- Create checks from Slack —
/solidping check https://example.comfor a quick HTTP check, or/solidping create <url>when you want to set the slug and interval. - Manage incidents from Slack — acknowledge and resolve without leaving the conversation.
- Sign in with Slack — use your Slack identity to log into the SolidPing dashboard.
- Link unfurling — paste a SolidPing check or status-page URL and see live status inline.
- App Home — open the SolidPing tab in Slack to see your active incidents at a glance.
Slash commands
| Command | What it does |
|---|---|
/solidping help | Show available commands |
/solidping check <url> | Create an HTTP check for a URL |
/solidping create <url> [-slug name] [-interval 30s] | Create a check, setting the slug and interval |
/solidping list | List your checks |
/solidping incidents | List active incidents |
/solidping comment [#42] <text> | Add a comment to an incident's timeline |
/solidping config | Configure where alerts are posted |
/solidping on its own, and anything it doesn't recognise, answers with this
list. Replies are ephemeral — only you see them.
If you installed SolidPing before this change, your workspace still has the
standalone /check and /comment commands registered with Slack, and will
until you reauthorize the app. They now reply telling you the command moved,
rather than doing anything.
Permissions we ask for and why
When you install SolidPing, Slack will show the list of permissions below. We only request what's needed for the integration to work.
| Scope | Why we need it |
|---|---|
chat:write, chat:write.public | Post incident alerts and command responses in your channels |
commands | Run the /solidping slash command |
app_mentions:read | Respond when you @mention SolidPing |
channels:read, groups:read | Let you pick which public or private channel receives alerts |
channels:history, groups:history | Read replies posted in the thread under a SolidPing incident alert, so your team's triage notes can be recorded on the incident timeline. Off by default — see below. |
im:write, im:history | Send you direct messages (onboarding, setup prompts, support replies) and receive your side of that conversation |
users:read, users:read.email | Match Slack users to SolidPing accounts when they sign in or interact with the bot |
reactions:write | React to incident messages (e.g. ✅ when an incident is resolved) |
links:read, links:write | Unfurl SolidPing URLs into rich previews |
The "Sign in with Slack" flow uses openid, profile, and email to identify you when logging in to the SolidPing dashboard.
Privacy and data
SolidPing for Slack stores only what's needed to send notifications and run commands: workspace ID and name, configured channel IDs, the bot token (encrypted), and the name and email of users who sign in via Slack or interact with the bot. We do not enumerate your workspace's member directory.
About message history. The channels:history and groups:history scopes are what make Slack deliver replies to us at all. What we do with them is deliberately narrow, and it is off unless you turn it on:
- Default (
explicit) — we ignore plain thread replies entirely. The only message text we store is what you deliberately send us: a/solidping commentslash command, or a direct message to the bot. - Opt-in (
all) — replies posted in the thread under a SolidPing incident alert are recorded as comments on that incident's timeline. Nothing else is: not other threads, not channel messages outside an incident thread, not message edits or deletions, and never a bulk read of your history.
We never export, archive, or search your workspace's messages, and we do not use any of your Slack data to train machine-learning models.
If you uninstall the app, we delete associated workspace data within 3 months.
Read the full Privacy Policy for details.
Support
Need help installing or using the integration? See Support for how to reach us, or open an issue on GitHub.