DEVOPS
PagerDuty Incident to GitHub Issue with Runbook Link
When a PagerDuty incident is triggered, it auto-creates a tracking GitHub issue in the owning service's repo, attaches the runbook link.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- LogicMap affected service to GitHub repo
- ActionFind matching runbook in repoGitHub
- ActionCreate labeled tracking GitHub issueGitHub
- OutputPost issue URL and runbook to PagerDuty incidentPagerDuty
What it does
This workflow turns a freshly triggered PagerDuty incident into a durable engineering artifact. It maps the alerting service to its GitHub repository, opens a labeled tracking issue, finds the matching runbook, and links everything back into PagerDuty so the responder lands on actionable context instead of a bare alert.
When to use it
Use it when on-call engineers waste the first minutes of an incident hunting for the right repo, runbook, and a place to track follow-up work. Best for teams with a clear service-to-repo mapping who want every page to leave a paper trail.
How it works
- 1A PagerDuty incident is triggered and fires the workflow.
- 2The workflow looks up the service-to-repo mapping for the affected service.
- 3It searches the repo for a `RUNBOOK.md` or matching runbook path.
- 4It creates a GitHub issue titled with the incident summary, labeled `incident`, including the alert details and runbook link.
- 5It posts the issue URL and runbook link as a note on the PagerDuty incident.
- 6The final step confirms the linkage so responders see the issue from the incident timeline.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.