Available now

Slack + OnCallReady: AI Incident Response for Slack Alerts

OnCallReady operates as an AI incident commander in your Slack workspace — intercepting alerts forwarded to a channel, autonomously executing fixes, and narrating every step in real time so your team is always informed without being woken up.

How it works

Configure your monitoring tools to forward alerts to your OnCallReady webhook. OnCallReady posts a live thread in #incidents, executes the runbook, and updates the thread as actions complete. If escalation is needed, it @mentions the on-call directly in the thread.

Monitoring tool (Datadog / Prometheus / Grafana) │ webhook POST → oncallready.polsia.app/api/alerts ▼ OnCallReady matches runbook → executes fix │ ├──▶ Slack #incidents ← live thread: status, actions, ETA ├──▶ Slack thread update ← each action logged as it runs └──▶ Slack resolved post ← resolution summary + audit link On escalation: @oncall is mentioned in thread with full diagnostic context

What it looks like in your channel

🤖

OnCallReady APP3:47 AM

🔴 ALERT — Disk Full on prod-web-02
Disk usage: 94% · Source: Datadog · Severity: Critical
Starting automated remediation now. No pages sent.

🤖

OnCallReady APP3:47 AM

▸ Identified top consumers: /var/log/nginx (8.2 GB), /tmp (2.1 GB)
▸ Rotated 7 day+ logs → freed 6.4 GB
▸ Purged /tmp stale files → freed 2.1 GB

🤖

OnCallReady APP3:48 AM

✓ RESOLVED — Disk usage now 61% · Duration: 28s
No human paged. View full audit trail →

Signal → Action table

Alert forwarded to Slack	Runbook triggered	Autonomous action + Slack update
Disk usage > 90%	Disk Full Remediation	Purge logs/tmp, post before/after disk stats to thread
Memory > 95% used	Memory Exhaustion	Drop caches, restart leaking service, post recovery confirmation
SSL cert expiring in 7 days	SSL Certificate Renewal	ACME renewal, deploy cert, post new expiry date to thread
Service health check failing	Service Restart & Recovery	Drain LB, restart, re-add, post uptime confirmation
Queue depth > threshold	Queue Backlog	Purge poison messages, scale workers, post queue depth trend
Escalation needed	Human escalation	@mention on-call in thread with full context and suggested next steps

Setup in 3 minutes

Point your existing monitoring webhook at OnCallReady, then configure where to post updates.

OnCallReady Slack config (environment variables)

# Add to your OnCallReady environment: SLACK_WEBHOOK_URL=https://hooks.slack.com/services/T.../B.../xxx SLACK_CHANNEL=#incidents SLACK_NOTIFY_ON_RESOLVE=true SLACK_MENTION_ONCALL_ON_ESCALATE=true SLACK_ONCALL_USER_ID=U12345678 # Slack member ID # Webhook for inbound alerts (same endpoint as always): POST https://oncallready.polsia.app/api/alerts { "title": "Disk usage > 90%", "source": "datadog", "severity": "critical" } # OnCallReady posts to #incidents automatically. # No Slack app install required — just an incoming webhook.

What stays on-call

OnCallReady handles the automatable incidents silently. These still page a human:

No matching runbook — escalated via @mention in thread with full diagnostic dump
Security alerts — always human-reviewed regardless of runbook match
Runbook execution fails twice — @mention fires immediately, thread preserved for context
Business-hours incidents you want human confirmation on — configurable per-alert-type
Post-mortems for P0 incidents — OnCallReady drafts the doc, human approves before publishing

The Slack integration works best alongside a monitoring source and a ticketing system:

Datadog → Jira → PagerDuty → Runbook library → Live demo →

Your #incidents channel should be boring

Let the AI commander handle the 3 AM noise. Connect in 3 minutes.

View pricing → Watch live demo