Pingoru Slack app — documentation

Install instructions, slash command reference, and troubleshooting for the native Pingoru Slack integration. Want a feature overview? See the marketing page.

Install

Sign into Pingoru at pingoru.io/login. You need a (free) account to install the Slack app — the workspace gets connected to a specific Pingoru account, which is where the alert routing rules live.
Open Integrations in the sidebar.
Click Add to Slack on the Slack tile.
Slack's consent screen opens. Pick the channel from the dropdown in the upper-right (if you're signed into multiple workspaces, switch using that dropdown), then click Allow.
You'll land back on the Integrations page with the channel connected. Test it by clicking Test on the channel row — a 🦘 ping arrives in your Slack channel within a second.

Want alerts in multiple channels? Click "Add to Slack" again and pick a different channel. Each install creates a separate integration row.

Slash commands

The /pingoru slash command works in any channel of your workspace once the app is installed. Responses are ephemeral — only you see them. Type /pingoru with no arguments for inline help.

Command	What it does
`/pingoru help`	Shows usage examples — same as typing /pingoru with no arguments.
`/pingoru aws`	Overall status for a provider plus any active incidents. The slug is typo-tolerant — gh, aws, gcp all resolve to their full names.
`/pingoru aws ec2`	Drill into a specific component. The first argument is the provider slug; the rest is the component name.
`/pingoru search openai`	Fuzzy multi-result search when you don't know the exact slug. Returns up to 8 matches with current status.

Slug aliases

Provider slugs are typo-tolerant via the same fuzzy resolver that powers our MCP API. A few common aliases:

aws → Amazon Web Services
gcp → Google Cloud
azure → Microsoft Azure
gh → GitHub
m365 / o365 → Microsoft 365
github actions → GitHub

Alert format

When an upstream provider opens, updates, or resolves an incident, Pingoru posts a Block Kit message to every Slack channel attached to a notification group monitoring that provider. The message contains:

Header: provider name and status pill (🟠 Partial Outage / 🔴 Major Outage / 🔧 Maintenance / ✅ Resolved)
Title: the incident headline as published upstream
Affected components: when the incident is scoped to a subset of the provider's catalog
Timestamps: started, resolved (in your local timezone via Slack's <!date^…> directive)
Action buttons: deep-link to the incident page on Pingoru and the provider's main page

Troubleshooting

Slash command says "failed with the error: dispatch_failed"

This usually means the Pingoru backend is briefly unreachable from Slack. Wait 10 seconds and try again. If it persists, check status.pingoru.io or contact support — Slack expects a 200 response within 3 seconds, so any backend slowness is surfaced this way.

Alerts stopped arriving after we changed our Slack channel name

Slack rotates the underlying webhook URL silently when a channel is renamed. Pingoru re-installs are the simplest fix: open Integrations, "Disconnect" the existing Slack channel, then click "Add to Slack" again to pick the renamed channel. Alerts resume on the next incident event.

I see "This app is not configured to handle interactive responses" on hover

Cosmetic warning only — the buttons in our messages are pure URL links and don't require an interactive callback. The warning means the workspace admin (you) hasn't yet enabled Slack's Interactivity feature on the app config. We've already configured a stub endpoint on Pingoru's side; if the warning bothers you, the workspace admin can ignore it. Clicking the buttons works regardless.

Can I post the same alert to multiple Slack channels?

Yes — each "Add to Slack" install lets Slack pick exactly one channel per workspace. To deliver to multiple channels in the same workspace, click "Add to Slack" once per channel. Each install creates a separate integration row in Pingoru, and you can attach different ones to different notification groups.

How do I uninstall the app cleanly?

Either side works: (1) on Pingoru, Integrations page → Disconnect on the Slack row; (2) in Slack, Workspace settings → Manage Apps → Pingoru → Remove. The other side syncs within a few seconds via Slack's app_uninstalled webhook.

How do I know which channel an alert will land in?

The integration row on /app/integrations shows the workspace name + channel name. Click "Manage in Slack" to open Slack's configuration page for that specific webhook — you can change the destination channel there.

Uninstall

You can remove the app from either side:

From Pingoru: open Integrations, click Disconnect on the Slack row.
From Slack: workspace settings → Manage Apps → Pingoru → Remove.

Either side syncs within a few seconds. Pingoru subscribes to Slack's app_uninstalled event, so a Slack-side removal disables the integration on Pingoru automatically.

Need more help?

Reach out at [email protected]. Bug reports + feature requests welcome.