Skip to content
PagerDuty logoGitHub logo

Connect PagerDuty to GitHub

Move data between PagerDuty and GitHub the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

PagerDuty triggers
3
PagerDuty actions
6
GitHub triggers
14
GitHub actions
19

Automation ideas

What you can build with PagerDuty and GitHub

A few flows teams run between PagerDuty and GitHub. Use one as a starting point, or build your own from scratch.

  • New Incident in PagerDuty creates Create Issue in GitHub

    Triggers when a new incident is created

  • New Pull Request in GitHub creates Create Incident in PagerDuty

    Triggers when there is activity on a pull request.

  • New Incident in PagerDuty creates Get issue information in GitHub

    Triggers when a new incident is created

  • New Pull Request in GitHub creates List Incidents in PagerDuty

    Triggers when there is activity on a pull request.

  • New Incident in PagerDuty creates Create comment on a issue in GitHub

    Triggers when a new incident is created

  • New Pull Request in GitHub creates Get Incident in PagerDuty

    Triggers when there is activity on a pull request.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in PagerDuty and acts in GitHub, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.