Webhook and Slack: PagerDuty Incident Acknowledgement Echo Template
This Spojit template mirrors every PagerDuty incident lifecycle event into a Slack channel so your on-call team sees triggers, acknowledgements, and resolutions in one place.
What It Builds
A Webhook trigger receives PagerDuty incident events, a Condition node branches on the event type, and a Slack Connector node posts a formatted message for each triggered, acknowledged, or resolved incident. Because PagerDuty has no native tile, Miraxa connects to its API through the http connector to pull extra incident detail (service, urgency, assignee) for richer Slack messages.
The Prompt
Paste this into Miraxa and it builds the workflow, connecting the tools for you:
Build a workflow with a webhook trigger that receives PagerDuty incident events. For each event, read the incident status and post a message to the #incidents Slack channel: green for resolved, yellow for acknowledged, red for triggered. Include the incident title, service name, urgency, and assignee. Connect to the PagerDuty API to fetch any missing incident details before posting.Connectors Used
- Webhook trigger - receives PagerDuty incident lifecycle events as they happen.
- http - how Miraxa connects to the PagerDuty API for incident enrichment.
- slack - posts the colour-coded incident message to your team channel.
Customize It
Change #incidents to your own channel, swap the colour mapping, or trim the fields in the Slack message. You can also tell Miraxa to skip low-urgency acknowledgements or to only echo triggered and resolved events.
Tips
- Add the PagerDuty webhook secret to the trigger so Spojit verifies each incoming payload.
- Use the Slack node in Direct mode for a fixed post action: no AI cost and predictable formatting.
- Give the http connection an API token with read access to incidents so enrichment lookups succeed.