Explore this workflow on its official n8n template page.
Tags
Jira SoftwareRelated workflows
See all Jira→
Incident Response Workflow - Part 3
This workflow is the third of three. You can find the other workflkows here: Incident Response Workflow - Part 1 Incident Response Workflow - Part 2 Incident Response Workflow - Part 3 We have the following nodes in the workflow: Webhook node: This trigger node listens to the event when the Resolve button is clicked. PagerDuty node: This node changes the status of the incident report from Acknowledged to Resolved in PagerDuty. Jira Software node: This node moves the incident issue to Done. Mattermost node: This node publishes a message in the auxiliary channel mentioning that the incident has been marked as resolved in PagerDuty and Jira. Mattermost node: This node publishes a message in the specified Incidents channel that the incident has been resolved by the on-call team.
Automate Figma Versioning and Jira Updates with n8n Webhook Integration
How It Works: This n8n template automates the process of tracking design changes in Figma and updating relevant Jira issues. The template is triggered when a new version is created in Figma via a custom plugin. Once the version is committed, the plugin sends the design details to an n8n workflow using a webhook. The workflow then performs the following actions: Fetches the Jira issue based on the provided issue link from Figma. Adds the design changes as a comment to the Jira issue. Updates the status of the Jira issue based on the provided task status (e.g., "In Progress", "Done"). This streamlines the workflow, reducing the need for manual updates and ensuring that both the design team and developers have the latest design changes and task statuses in sync. How to Use It: Set up the Figma Plugin: Install the Figma Commit Plugin from GitHub. In the plugin, fill out the version name, design link, Jira issue link, and the task status. Commit the changes in Figma, which will trigger the webhook. Set Up the n8n Workflow: Import this template into your n8n instance. Connect the Figma Trigger node to capture version updates from Figma. Configure the Jira nodes to retrieve the issue and
Manage custom incident response in PagerDuty and Jira
This workflow automatically follows the steps in a custom incident response playbook and manages incidents in PagerDuty, Jira tickets, and notifies the on-call team in Mattermost. This workflow consists of three sub-workflows, each automating specific steps in the playbook. Read more about this use case and learn how to set up the workflows step-by-step in the blog tutorial How to automate every step of an incident response workflow. Prerequisites A PagerDuty account and credentials A Mattermost account and credentials A Jira account and credentials Nodes Webhook nodes trigger the workflows when an incident is created in PagerDuty, and when the incidedent is acknowledged and resolved. Mattermost nodes create an auxiliary channel for the on-call team to discuss the incident with buttons to acknowledge the incident and mark it as resolved. PagerDuty nodes update the status of the incident. Jira nodes create an issue about the incident and update its status when it's resolved.