Incident Response Part 3: Resolve PagerDuty, Jira & Notify Mattermost

This workflow is the final part of a three-part incident response automation series. It triggers via a Webhook when the 'Resolve' button is clicked, typically from Part 2. It then uses the PagerDuty node to update the incident status from Acknowledged to Resolved, ensuring the on-call system reflects the closure accurately.

Next, the Jira Software node takes the issue key from the webhook payload and moves the corresponding Jira ticket to 'Done', streamlining ticket lifecycle management across tools. Two Mattermost nodes follow: one posts a confirmation message to an auxiliary channel (dynamically pulled from the webhook), stating the issue is closed in both PagerDuty and Jira; the other announces resolution in a dedicated Incidents channel, including incident summary and team credit.

Benefits include reduced manual updates across siloed tools, minimizing errors and response times during high-pressure incidents. It ensures all stakeholders are instantly notified, improving team coordination. Ideal for IT/Security teams in healthcare or any ops environment handling PagerDuty-monitored incidents with Jira tracking, saving hours per incident on routine closures.