Slack integration

Outage alerts in Slack — without the noise.

Native Slack app for Pingoru. Rich Block Kit messages when your upstream providers break, and a /pingoru slash command for ad-hoc status checks — all without leaving your workspace.

Free with every Pingoru account. No bot user, no message-content scopes.

Two ways to stay informed.

📬 Passive — alerts when things break

When an upstream provider you monitor opens, updates, or resolves an incident, Pingoru posts a rich Block Kit message to the channel you picked during install:

🟠 OpenAI — Partial Outage
Elevated error rates affecting ChatGPT and API responses
Affected: ChatGPT, API, Dashboard
Started: Today 5:25 PM
View incident Provider page

Each alert is filtered against the notification group it belongs to — so you only see incidents on providers you actually care about, at the impact levels you've set.

⚡ Active — /pingoru slash command

Need to check before reporting "is X down?" to your team? Type the slug, hit enter, get the current status:

/pingoru aws
🟠 Amazon Web Services — Partial Outage
🟠 Increased Error Rate and Latency · EC2 N. Virginia
View on Pingoru

Typo-tolerant: /pingoru gh finds GitHub, /pingoru aws ec2 drills into a component, /pingoru search openai does a fuzzy multi-result lookup. Responses are private — only you see them.

Why not just use a webhook?

Pingoru already supports plain incoming webhooks. The native app adds a few things webhooks can't:

  • One-click install. No copy-pasting webhook URLs or signing secrets — Slack's OAuth flow picks the channel for you.
  • Block Kit rendering. Status pills, affected-component lists, action buttons rendered as native Slack UI — not a wall of text.
  • /pingoru slash command. Webhooks are one-way; the app gives you query-on-demand without leaving Slack.
  • Auto-cleanup. If a Slack admin removes the app, Pingoru gets the app_uninstalled event and stops trying to deliver — no error spam in your audit log.
  • Visible install state. Slack admins can see which channels Pingoru posts to and revoke per-channel access from Slack's UI without touching Pingoru's dashboard.

The webhook integration stays available too — it's the right choice for Discord, Teams, internal tooling, or any URL that isn't Slack.

FAQ

What does the Pingoru Slack app do?

It posts incident alerts directly to your Slack channels (with rich Block Kit messages) and adds a /pingoru slash command for ad-hoc status checks. Two channels of integration: passive notifications when something breaks, and active queries when you want to check before reporting an issue.

How do I install it?

Sign into Pingoru at pingoru.io, go to Integrations in your dashboard, click "Add to Slack", choose the channel during Slack's OAuth consent screen, and you're done. Takes about 30 seconds.

Do I need a paid plan?

No — the Slack app is free for all Pingoru accounts. Free-plan limits on the number of monitors still apply, but the Slack integration itself doesn't cost extra.

What does the slash command do?

Type /pingoru aws in any channel to see the current status of AWS plus any active incidents. /pingoru aws ec2 drills into a specific component. /pingoru search openai does a fuzzy lookup. Responses are ephemeral by default — only you see them.

Can I send alerts to multiple channels?

Yes. Each "Add to Slack" install lets Slack pick one channel per workspace. To deliver to multiple channels, install once per channel — they'll all show up in your Pingoru integrations list. You can then attach different channels to different notification groups.

How do I remove the integration?

Two ways: (1) on Pingoru, open Integrations and click "Disconnect" on the Slack row; (2) in Slack, go to your workspace settings → Manage Apps → Pingoru → Remove. Either side syncs cleanly — alerts stop within seconds.

Add Pingoru to your Slack in 30 seconds.

Free with every Pingoru account. Connects to any of your monitored providers — install once, get incident alerts going forward.