Bring incident updates into one place. When a new PagerDuty event arrives, a Jira issue is created and your Mattermost channel gets clear alerts. Teammates can acknowledge or resolve from chat and the status stays in sync across tools.

Three webhooks drive the flow. The main webhook receives PagerDuty payloads and sends two Mattermost messages with the incident summary and link, then creates a Jira ticket in the right project and type with a set assignee. A second webhook handles acknowledge requests, sets the PagerDuty incident to acknowledged, and posts a confirmation to the same Mattermost channel using the channel_id in the request. The third webhook handles resolve, marks the PagerDuty incident as resolved, updates the Jira issue to a closed status, and notifies the channel. The acknowledge and resolve endpoints expect the PagerDuty incident ID and the Jira key in the request body, which can be sent by a Mattermost slash command or button.

You will need accounts and API access for PagerDuty, Jira Software Cloud, and Mattermost. Map your Jira project, issue type, and assignee, and point the PagerDuty webhook to the n8n URL. Expect faster handoffs, fewer mistakes, and clear chat updates for on call, SRE, and IT support teams. Many teams reduce manual updates from several steps to one quick action, cutting work from about 30 minutes to under 5 minutes per incident.

• Three webhook endpoints handle event intake, acknowledge, and resolve actions
• Creates Jira issues with the event title, project, type, and a set assignee
• Sends clear Mattermost alerts with incident summaries and links
• Updates PagerDuty incidents to acknowledged and resolved from chat requests
• Moves Jira issues to a specific closed status when incidents resolve
• Uses channel_id from requests to post in the correct Mattermost channel
• Secures connections with API tokens for Jira, PagerDuty, and Mattermost

• Reduce manual work from 30 minutes to 5 minutes per incident
• Streamline incident updates by about 90 percent across tools
• Cut status mismatches between PagerDuty and Jira by about 90 percent
• Connect PagerDuty, Jira, and Mattermost in one flow
• Keep teams informed in one channel with real time posts

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with PagerDuty, Jira Software Cloud and Mattermost. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create Jira Software Cloud credentials. Use your site URL, email, and an API token from your Atlassian account. Name the credential clearly and attach it to both Jira nodes.
4. In the n8n credentials manager, create a PagerDuty API token credential. Generate a read write token in your PagerDuty dashboard and attach it to both PagerDuty nodes.
5. In the n8n credentials manager, create a Mattermost credential. Provide your server URL and a personal access token with permissions to post to channels. Attach it to all Mattermost nodes.
6. Open the main Webhook node in n8n and copy the production URL. In your PagerDuty service settings, add a webhook subscription that points to this URL and enable incident trigger and update events.
7. Open the Jira create issue node and set the correct project, issue type, and default assignee. Confirm the summary is mapped from the PagerDuty event title.
8. Open the Jira update issue node and set the target closed status ID used in your workflow. Replace the default status ID if it differs.
9. Create a Mattermost slash command or button for acknowledge that calls the Ack webhook URL. Include channel_id and send the PagerDuty incident ID and Jira key in the payload fields expected by the workflow.
10. Create a Mattermost slash command or button for resolve that calls the Resolve webhook URL. Send the same fields so the flow can update both PagerDuty and Jira.
11. Trigger a test incident in PagerDuty. Verify a Jira issue is created and initial Mattermost messages appear with the summary and link.
12. Run the acknowledge command in Mattermost with the incident ID and Jira key. Confirm PagerDuty shows acknowledged and the channel receives a confirmation message.
13. Run the resolve command. Check that PagerDuty marks the incident resolved, the Jira issue moves to the closed status, and final notifications post to the channel.
14. If something fails, check API tokens and permissions. Verify the Jira project and status IDs, confirm the PagerDuty incident ID sent in the request body, and ensure the Mattermost token can post to the target channel.