Create your own GitHub and PagerDuty integration

Choose a triggerChoose an action

Choose a trigger

Choose an action

When GitHub: Deployment status updated happens, do PagerDuty: Create incident.

Get started with GitHub and PagerDuty on Corsair Hub

Complete your first operation in <1 min

Get started

Popular GitHub 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.

Page on-call when production deploy fails

When a GitHub deployment status is failure for production, create a PagerDuty incident with commit SHA.

TriggerDeployment status updated

ActionCreate incident

GitHub + PagerDutyTry it →

Attach recent commits when incidents fire

When a PagerDuty incident triggers, list commits on main from the last hour and add as an incident note.

TriggerIncident triggered

ActionList commits

PagerDuty + GitHubTry it →

Open low-urgency incident on main CI failure

When a required check fails on main, create a sev-2 PagerDuty incident for the build cop rotation.

TriggerCheck run completed

ActionCreate incident

GitHub + PagerDutyTry it →

Resolve incident when workflow goes green

When the deploy workflow completes successfully, resolve linked PagerDuty incidents automatically.

TriggerWorkflow run completed

ActionUpdate incident

GitHub + PagerDutyTry it →

Log release tag on active incidents

When a release publishes during an open incident, add the tag and changelog link to PagerDuty notes.

TriggerRelease published

ActionAdd incident note

GitHub + PagerDutyTry it →

Comment on GitHub when incident is acked

When an incident is acknowledged, comment on the related deployment issue with the responder name.

TriggerIncident acknowledged

ActionComment on issue

PagerDuty + GitHubTry it →

Agent

Use Corsair's MCP with your agent

Corsair connected

The agent searches both apps before it answers.

Did the outage correlate with today's production deploy?

PagerDuty incident #INC-4412 opened at 14:03 UTC for elevated API errors, currently acknowledged by Priya on the platform rotation. GitHub shows a production deployment at 13:58 UTC from commit d4e19aa (PR #902 payment retries). Workflow runs were green, but deployment status flipped to failure four minutes before the page. Recent commits on main include two payment service changes within the same hour.

GitHub and PagerDuty details

GitHub

Code hosting platform for repositories, issues, pull requests, and developer workflows.

See GitHub integration GitHub docs

PagerDuty

Incident response platform for on-call schedules, alerts, and operational reliability workflows.

See PagerDuty integration PagerDuty docs

GitHub and PagerDuty FAQ

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

Yes. Connect both apps once, then page on-call when deploys or CI fail, attach commits to incidents, and resolve pages when workflows recover.

Create incidents from failed deploys and checks, enrich pages with recent commits, auto-resolve on green builds, log releases during outages, and sync acks back to GitHub.

Yes. GitHub deployment, check, workflow, and release events plus PagerDuty incident lifecycle webhooks are available as typed triggers with tenant matching built in.