Create your own Slack and PagerDuty integration

Choose a trigger
Choose an action

When Slack: A new channel was created in the workspace happens, do PagerDuty: List notes for an incident.

Popular Slack and PagerDuty workflows

When this happens in one app, do this in the other. Try it on Hub to connect both apps and run the pair.

Most popular

Create #incident channel on trigger

When PagerDuty triggers a sev-1, post the incident title, service, and join link to #incidents-war-room.

PagerDuty + SlackTry it →

Post acks to the war room thread

When an incident is acknowledged, reply in Slack with who acked and the PagerDuty incident URL.

PagerDuty + SlackTry it →

Announce resolves with duration

When an incident resolves, post resolution time and link to the postmortem template in Slack.

PagerDuty + SlackTry it →

Notify channel on reassignment

When PagerDuty reassigns an incident, update the Slack thread with the new on-call engineer.

PagerDuty + SlackTry it →

Pin latest status from Slack reactions

When on-call reacts with :eyes: on the incident post, fetch PagerDuty log entries and pin a status summary.

Slack + PagerDutyTry it →

Agent

Use Corsair's MCP with your agent

Corsair connected

The agent searches both apps before it answers.

Who is on call for payments and is anything still open?

Slack and PagerDuty details

Slack and PagerDuty FAQ

Yes. Corsair is built with a REST API. This means you can build agents, knowledge bases, interfaces, and workflows.

Yes. With Corsair you connect both apps once, then automate in either direction between Slack and PagerDuty.

Broadcast triggered, acknowledged, and resolved incidents to Slack war rooms, keep threads updated on reassignment, and pull log entries when on-call reacts in channel.

Yes. Slack and PagerDuty events are available as typed webhooks with tenant matching built in, so workflows and agents react as soon as something changes.