Back to Integrations
integration integration
integration Jira Software node

Integrate Jira Software with 500+ apps and services

Unlock Jira Software’s full potential with n8n, connecting it to similar Development apps and over 1000 other services. Automate productivity workflows by scheduling tasks, managing project timelines, and tracking progress across platforms. Create adaptable and scalable workflows between Jira Software and your stack. All within a building experience you will love.

Create workflows with Jira Software integrations

797 integrations
Sort by:
Popularity
NameOldestNewest

Popular ways to use Jira Software integration

Webhook node
Mattermost node
Jira Software node

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.
tanay1337
tanaypant
Webhook node
Mattermost node
Jira Software node
PagerDuty node

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.
tanay1337
tanaypant
Webhook node
Jira Software node

Create Unique Jira tickets from Splunk alerts

The workflow is an automated process designed for incident management and tracking, specifically by integrating Splunk alerts with a Jira ticketing system using n8n. The initial step in the workflow is a Webhook Trigger, which is set up to receive POST requests with data from Splunk to initiate the workflow. Once the workflow is triggered, the "Set Host Name" node cleans up the hostname received from Splunk, ensuring that it is alphanumeric for consistency and security purposes. Subsequently, the "Search Ticket" node interacts with Jira through a Jira Query Language (JQL) request to locate any existing issues that match the sanitized hostname. The workflow splits at the "IF Ticket Not Exists" node, which checks for the presence of a key indicating a matching issue. If an issue exists, the workflow proceeds to add a comment to the identified issue, and if not, it creates a new Jira issue. At the false path, the "Add Ticket Comment" node appends a new comment to the existing Jira issue, encapsulating details from the Splunk alert, such as the timestamp and the alert description.
n8n-team
n8n Team
Slack node
Jira Software node
+10

Automate Customer Support Issue Resolution using AI Text Classifier

This n8n template is designed to assist and improve customer support team member capacity by automating the resolution of long-lived and forgotten JIRA issues. How it works Schedule Trigger runs daily to check for long-lived unresolved issues and imports them into the workflow. Each Issue is handled as a separate subworkflow by using an execute workflow node. This allows parallel processing. A report is generated from the issue using its comment history allowing the issue to be classified by AI - determining the state and progress of the issue. If determined to be resolved, sentiment analysis is performed to track customer satisfaction. If negative, a slack message is sent to escalate, otherwise the issue is closed automatically. If no response has been initiated, an AI agent will attempt to search and resolve the issue itself using similar resolved issues or from the notion database. If a solution is found, it is posted to the issue and closed. If the issue is blocked and waiting for responses, then a reminder message is added. How to use This template searches for JIRA issues which are older than 7 days which are not in the "Done" status. Ensure there are some issues that meet this criteria otherwise adjust the search query to suit. Works best if you frequently have long-lived issues that need resolving. Ensure the notion tool is configured as to not read documents you didn't intend it to ie. private and/or internal documentation. Requirements JIRA for issues management OpenAI for LLM Slack for notifications Customising this workflow Why not try classifying issues as they are created? One use-case may be for quality control such as ensuring reporting criteria is adhered to, summarising and rephrasing issue for easier reading or adjusting priority.
jimleuk
Jimleuk
HTTP Request node
Slack node
Jira Software node
+2

Analyze CrowdStrike Detections - Search for IOCs in VirusTotal - Create a Ticket in Jira, and Post a Message in Slack

This n8n workflow automates the handling of security detections from CrowdStrike, streamlining incident response and notification processes. The workflow is triggered daily at midnight by the Schedule Trigger node. It begins by fetching recent security detections from CrowdStrike using an HTTP Request node. The response is then split into individual detections for further processing. Each detection is enriched by querying the CrowdStrike API for detailed information using another HTTP Request node. The workflow then processes these detections sequentially using the Split In Batches node. Next, it looks up behavioral information associated with each detection in VirusTotal using two HTTP Request nodes. One node queries VirusTotal based on SHA256 values, and the other based on IOC (Indicator of Compromise) values. The workflow includes a 1-second pause using the Wait node to prevent rate limiting when making requests to the VirusTotal API. Subsequently, the workflow sets fields with relevant details from both CrowdStrike and VirusTotal, including detection links, confidence scores, filenames, usernames, and more. These details are concatenated using an Item Lists node for each detection. The final step involves creating Jira issues for each detection, including summaries with CrowdStrike alert severity and hostnames, as well as descriptions that incorporate information from CrowdStrike and VirusTotal. Information about this issue is then sent via a Slack message to a Slack user. Potential issues during setup might include configuring the Schedule Trigger node to trigger at the correct time zone and handling potential rate limiting from the VirusTotal API, which could lead to throttled requests. Additionally, the note about a possible typo in the URL for the Virustotal nodes should be addressed to ensure correct API calls. The Jira node may need to be replaced with the latest version for compatibility. Properly configuring API credentials and handling errors that may occur during API requests are essential for a smooth workflow operation. Careful testing with sample data is recommended to validate the workflow's functionality and ensure it aligns with your organization's security incident response processes.
n8n-team
n8n Team

Supported Actions

Changelog
Get issue changelog
Create
Create a new issue
Delete
Delete an issue
Get
Get an issue
Get Many
Get many issues
Notify
Create an email notification for an issue and add it to the mail queue
Status
Return either all transitions or a transition that can be performed by the user on an issue, based on the issue's status
Update
Update an issue
Add
Add attachment to issue
Get
Get an attachment
Get Many
Get many attachments
Remove
Remove an attachment
Add
Add comment to issue
Get
Get a comment
Get Many
Get many comments
Remove
Remove a comment
Update
Update a comment
Create
Create a new user
Delete
Delete a user
Get
Retrieve a user
Jira Software node

About Jira Software

Jira is a unique project management tool for software developers that started as an issue tracking platform. Jira Software offers the same features of Jira Core, and also includes additional Agile functionalities.

Related categories

Similar integrations

  • Google Sheets node
  • MySQL node
  • Postgres node
  • Notion node
  • GitHub node
  • Google Calendar node
  • MongoDB node
  • Microsoft SQL node
  • Notion Trigger node
  • GraphQL node
Use case

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

Over 3000 companies switch to n8n every single week

Connect Jira Software with your company’s tech stack and create automation workflows

in other news I installed @n8n_io tonight and holy moly it’s good

it’s compatible with EVERYTHING

We're using the @n8n_io cloud for our internal automation tasks since the beta started. It's awesome! Also, support is super fast and always helpful. 🤗

Last week I automated much of the back office work for a small design studio in less than 8hrs and I am still mind-blown about it.

n8n is a game-changer and should be known by all SMBs and even enterprise companies.

FAQ about Jira Software integrations

  • How can I set up Jira Software integration in n8n?

      To use Jira Software integration in n8n, start by adding the Jira Software node to your workflow. You'll need to authenticate your Jira Software account using supported authentication methods. Once connected, you can choose from the list of supported actions or make custom API calls via the HTTP Request node, for example: you can then configure the parameters for your chosen actions, such as creating issues, updating issues, or querying projects. Make sure to test your integration to ensure everything is functioning as expected. Finally, save your workflow and monitor its execution.

  • Do I need any special permissions or API keys to integrate Jira Software with n8n?

  • Can I combine Jira Software with other apps in n8n workflows?

  • What are some common use cases for Jira Software integrations with n8n?

  • How does n8n’s pricing model benefit me when integrating Jira Software?

Implement complex processes faster with n8n

red icon yellow icon red icon yellow icon