Integrations

Slack-first incident RCA

Run /incident in Slack, @mention the bot, or paste war-room threads in the app: no migration, no SDK.

Pro & Team only: full in-channel workflows from Account → Add to Slack: Slack is not available on the Starter (free) plan. Team adds GitHub deploy automation when onboarded. CloudWatch, Loki, and PagerDuty are on the roadmap (paste-in or native later).

Primary integration · Live

Slack · App & incident engine

The default way teams run ProdRescue during live incidents.

Slash command: /incident with an optional thread URL, or run it in-channel for latest activity (Pro / Team).
Mentions: @ProdRescue in a thread or channel for the same RCA flow.
App: paste Slack permalinks or fetch threads after you connect the workspace under Account.

Add to Slack

Slack integration is on Pro & Team: ~30 seconds to connect, invite the bot to #incidents after.

End-to-end flow

1Slack `/incident` + threads: stay in the war room

2Evidence-backed RCA (+ deploy context on Team with GitHub)

3Actionable resolution: remediations you can ship

Also available

GitHub: Deploy + repo automation

Live · Team onboarding

Team (onboarded with us): connect repos in Account: webhooks run deploy analysis on qualifying events; suggested fixes are reviewed in-app before anything hits GitHub. Pro stays Slack + paste-in RCA without repo automation.

More log & alert sources (roadmap)

Today you paste logs or pull from Slack. Native connectors below are planned: expand to see CloudWatch, Loki, and PagerDuty.

Soon

CloudWatch: Logs

Export logs from AWS CloudWatch and get auto-structured incident analysis with timeline and root cause.

Soon

Grafana Loki: Logs

Paste Loki log excerpts into ProdRescue and get structured documentation and RCA in minutes.

Soon

PagerDuty: Alerts

Incidents and alerts from PagerDuty auto-included in your executive report for a single source of truth.

Slack setup guide

Connect once, invite the bot once, then run incidents directly in channel.

Add to Slack

1) Connect & invite

Sign in → Account → Add to Slack.
Open incident channel (e.g. #prod-alerts).
Run /invite @ProdRescue AI.

2) Trigger analysis

/incident → latest thread / channel activity
/incident [thread URL] → specific thread
@ProdRescue AI mention → same RCA flow

3) Common fixes

Wrong workspace? Go to Account → Slack → Disconnect, then Add to Slack again with the correct workspace.

Need Channel ID? Copy channel link and use the token after archives/.

/incident/incident [thread URL]@ProdRescue AI

Need a direct integration?

Custom integrations available for:

DatadogSentryKubernetesPagerDutyInternal log pipelines

Contact Sales

Custom integrations

Available via private deployment:

On-prem log pipelines
VPC integration
Direct API ingestion
Designed for SOC 2 compliance readiness

Contact Sales