Automated remediation for PagerDuty incidents by type
Build a workflow that receives PagerDuty v3 webhooks for incident lifecycle events. Branch on incident type/payload to choose the matching remediation routine (e.g., enrich an IP with GreyNoise, restart a service, or annotate the incident). Apply the remediation, annotate the PagerDuty incident with what was done, and acknowledge/resolve when appropriate. Verify the webhook signature, ignore irrelevant event types, and retry failures. Output the remediation taken per incident.
What this prompt builds
React to PagerDuty incident webhooks and run type-specific remediation automatically.
The problem
On-call engineers are paged for incidents that often have a known, repeatable fix, burning attention on toil at all hours. Manual response is slow and inconsistent between responders.
Solution and impact
This workflow receives PagerDuty v3 webhooks for triggered, annotated, and acknowledged incidents and runs a remediation path tailored to the incident type, enriching with GreyNoise where relevant. Common incidents self-heal and humans focus on the genuinely novel.