Jira Automation Workflows
170 ready-made Jira workflows for n8n, Make, Zapier, Activepieces, and Pipedream. Issue tracking automations for engineering and support teams.
Automate Comprehensive Jira Project Setup with AI and Form Integration
Streamline the creation of detailed Jira projects by transforming raw project ideas into structured user stories and sub-tasks using AI and automated Jira integration. Ideal for Agile teams and project managers.
n8n$24.99Automate Daily Jira Ticket Summaries with AI and Email Delivery
Streamline your Jira ticket management by automating the fetching, analysis, and summarization of daily tickets with AI, and deliver comprehensive reports via email.
n8n$14.99Automate GitLab Merge Request Code Reviews with AI and JIRA Integration
Streamline code reviews by automatically generating AI-driven feedback on GitLab merge requests, incorporating JIRA ticket context for enhanced insights.
n8n$19.99Automate HubSpot to Jira Ticket Classification and Routing with AI
Streamline your customer support workflow by automatically classifying and routing HubSpot tickets to Jira using AI for sentiment analysis and categorization.
n8n$14.99Automate JIRA Ticket Triage and Resolution with AI
This n8n workflow automates the triage and resolution of support tickets in JIRA using AI. It enhances efficiency by labeling, prioritizing, and attempting to resolve issues based on historical data.
n8n$14.99Automate Slack Helpdesk with AI, Supabase, and JIRA Integration
Streamline your Level 1 IT support by automating repetitive tasks with AI-driven assistance, integrating Slack, Supabase, and JIRA for efficient ticket management.
n8n$14.99Automate Agile Retrospective Reports from Jira Epics Using AI and Google Docs
Streamline the creation of Lessons Learned reports by automating the process when a Jira Epic is marked as Done. This workflow uses AI to generate insightful reports and delivers them directly to Google Docs.
n8n$9.99AI-Powered Email to Jira Ticket Creation with Llama 3.2
This AI-powered workflow reads emails, understands the request using an LLM, and creates structured Jira issues. ### Key Insights - Poll for new emails every 5 minutes; ensure Gmail/IMAP is properly configured. - AI analysis requires a reliable LLM model (e.g., Chat Model or AI tool). ### Workflow Process - Trigger the workflow with the `Check for New Emails Gmail Trigger` node. - Fetch full email content using the `Fetch Full Email Content get message` node. - Analyze email content with the `Analyze Email & Extract Tasks` node using AI. - Parse the AI-generated JSON output into tasks with the `Parse JSON Output from AI` node. - Create the main Jira issue with the `Jira - Create Main Issue create: issue` node. - Split subtasks from JSON and create them with the `Split Subtasks JSON Items` and `Create Subtasks create: issue` nodes. ### Usage Guide - Import the workflow into n8n and configure Gmail and Jira credentials. - Test with a sample email to ensure ticket creation and subtask assignment. ### Prerequisites - Gmail/IMAP credentials for email polling - Jira API credentials with issue creation permissions ### Customization Options Adjust the `Analyze Email & Extract Tasks` node to refine AI task extraction or modify the polling frequency in the trigger node.
n8n$9.99Automate Customer Support with AI, Outlook, and JIRA
Streamline customer support by automating ticket creation and routing using AI classification from emails and web forms. This workflow integrates with Outlook, OpenAI, and JIRA to efficiently manage support requests.
n8n$14.99Automated Error Log Monitoring with Slack Alerts and Jira Ticket Creation
This workflow automates the monitoring of server error logs, sending alerts via Slack and creating Jira tickets for critical issues. It ensures developers are promptly notified of both critical and non-critical errors.
n8n$14.99Automate Resolution of Long-Standing JIRA Issues with AI Integration
Enhance your customer support efficiency by automating the resolution of long-standing JIRA issues using AI-powered classification and sentiment analysis.
n8n$19.99Automate Android Feature Flag Cleanup with GitLab, LaunchDarkly, Jira, and Slack
This n8n workflow automates the detection and management of unused feature flags in Android Kotlin/Java codebases by comparing GitLab repository code with LaunchDarkly's feature flag list. It logs results in Google Sheets, creates Jira tickets for cleanup, and sends Slack alerts.
n8n$9.99Automate Release Notes Generation and Distribution with GitHub, JIRA, and Google Gemini
Streamline your software release process by automatically generating and emailing professional release notes using GitHub, JIRA, and Google Gemini.
n8n$14.99Automate GitHub PRs & JIRA Updates from Git Commit Commands - Single Repo
## This n8n template from [Intuz](https://www.intuz.com/) delivers a complete and automated solution to streamline your development workflow for a single repository. By embedding specific keywords and a JIRA issue ID within your git commit commands, this workflow automatically creates a Pull Request in GitHub and simultaneously updates the corresponding JIRA ticket. This provides a complete, seamless integration that eliminates manual steps and keeps your project management perfectly in sync with your codebase. ## How it works This workflow acts as a powerful bridge between your Git repository and your project management tools, driven entirely by the structure of your commit messages. 1. **GitHub Webhook Trigger:** The workflow starts when a developer pushes a new commit to a specified repository in GitHub. 2. **Parse Commit Message:** A Code node extracts key information from the commit message: - The JIRA Issue Key (e.g., FF-1196). - The base branch for the PR (e.g., development). - Action commands like [auto-pr] and [taskcompleted]. 3. **Conditional PR Creation:** An IF node checks if the [auto-pr] command is present. - If yes, it uses the GitHub node to automatically create a pull request from the developer's branch to the specified base branch. - If no, this step is skipped, allowing for multiple commits before a PR is made. 4. **Conditional JIRA Update**: Another IF node checks for the [taskcompleted] command. - If yes, it uses the JIRA node to transition the corresponding issue to your Done status (e.g., Task Completed or In Review). - If no, the JIRA issue remains in its current state, perfect for work-in-progress commits. ## How to Use: Quick Start Guide 1. Click the Use Template button to import this workflow into your n8n instance. 2. Configure the GitHub Trigger: - Open the GitHub Push Trigger node. It will display a unique Webhook URL. Copy this URL. - In your GitHub repository, go to Settings > Webhooks > Add webhook. - Paste the URL into the Payload URL field. - Set the Content type to application/json. - Under "Which events would you like to trigger this webhook?", select Just the push event. - Click Add webhook. 3. Connect Your Accounts: - GitHub: Select your GitHub API credential in the Create Pull Request node. - JIRA: Select your JIRA API credential in the Update JIRA Issue Status node. 4. Customize the JIRA Transition (Important): - Open the Update JIRA Issue Status node. - In the Transition parameter, you need to set the specific status you want to move the issue to (e.g., Done, Completed, In Review). You can use the ID or the exact name of the transition from your JIRA projects workflow. 5. Activate the Workflow: Save your changes and activate the workflow. You're ready to automate! ## Example Commit Message: git commit -m "FF-1196 Implement OAuth login [auto-pr,development,taskcompleted]" ## Key Requirements to Use Template - An active n8n instance. - A GitHub account with repository admin permissions to create webhooks. - A JIRA Cloud account with permissions to update issues. - Developers who can follow the specified git commit message format. ## Connect with us - Website: https://www.intuz.com/services - Email: getstarted@intuz.com - LinkedIn: https://www.linkedin.com/company/intuz - Get Started: https://n8n.partnerlinks.io/intuz ## For Custom Workflow Automation Click here - [Get Started](https://www.intuz.com/get-started)
n8n$14.99Automate JIRA Issue Creation from Outlook Support Emails
This n8n workflow automates the process of creating JIRA issues from support requests received in an Outlook shared inbox. It uses AI to triage and label requests, ensuring efficient issue management.
n8n$9.99Automate IT Support Requests from Telegram Voice Messages to JIRA Tickets
Streamline IT support by converting Telegram voice messages into JIRA tickets using OpenAI Whisper for transcription and GPT-4.1 for data extraction.
n8n$14.99Auto-Create GitHub PRs & JIRA Updates from Git Commit Commands (Multi-Repo)
# This n8n template from [Intuz](https://www.intuz.com/) provides a complete and automated solution for scaling your DevOps practices across multiple repositories. Are you tired of the repetitive dance between git push, creating a pull request in GitHub, updating the corresponding task in JIRA, and then manually notifying your team in Slack or Notion? This template puts your entire post-commit workflow on autopilot, creating a seamless and intelligent bridge between your code and your project management. By embedding specific keywords and a JIRA issue ID into your git commit commands, this workflow automatically creates a Pull Request in the correct GitHub repository and updates the corresponding JIRA ticket. This creates a complete, centralized system that keeps all your projects synchronized, providing a massive efficiency boost for teams managing a diverse portfolio of codebases. ## Who This Template Is For? This template is a must-have for any organization looking to streamline its software development lifecycle (SDLC). It's perfect for: - Development Teams: Eliminate tedious, manual tasks and enforce a consistent workflow, allowing developers to stay focused on coding. - DevOps Engineers: A ready-to-deploy solution that integrates key developer tools without weeks of custom scripting. - Engineering Managers & Team Leads: Gain real-time visibility into development progress and ensure processes are followed without constant check-ins. - Project Managers: Get accurate, automatic updates in JIRA the moment development work is completed, improving project tracking and forecasting. ## Step-by-Step Setup Instructions Follow these steps carefully to configure the workflow for your environment. **1. Connect Your Tools (Credentials)** - GitHub: Create credentials with repo scope to allow PR creation. - JIRA: Create an API token and connect your JIRA Cloud or Server instance. - Slack: Connect your Slack workspace using OAuth2. - Notion: Connect your Notion integration token. **2. Configure the GitHub Webhook (For Each Repository)** This workflow is triggered by a GitHub webhook. You must add it to every repository you want to automate. - First, Save and Activate the n8n workflow to ensure the webhook URL is live. - In the n8n workflow, copy the Production URL from the Webhook node. - Go to your GitHub repository and navigate to Settings > Webhooks > Add webhook. - In the Payload URL field, paste the n8n webhook URL. - Change the Content type to application/json. - Under "Which events would you like to trigger this webhook?", select "Just the push event". - Click Add webhook. Repeat this for all relevant repositories. **3. Configure the JIRA Nodes (Crucial Step)** Your JIRA project has unique IDs for its statuses. You must update the workflow to match yours. - Find the two JIRA nodes named "Update task status after PR" and "Update the task status without PR". - In each node, go to the Status ID field. - Click the dropdown and select the status that corresponds to "Done" or "Development Done" in your specific JIRA project workflow. The list is fetched directly from your connected JIRA instance. **4. Configure Notification Nodes** Tell the workflow where to send updates. - For Slack: Open the two nodes named "Send message in slack..." and select your desired channel from the Channel ID dropdown. - For Notion: Open the two nodes named "Append a block in notion..." and paste the URL of the target Notion page or database into the Block ID field. **5. Final Activation** Once all configurations are complete, ensure the workflow is Saved and the toggle switch is set to Active. You are now ready to automate! ## Customization Guidance This template is a powerful foundation. Here's how you can adapt it to your team's specific needs. **1. Changing the PR Title or Body:** - Go to the "Request to create PR (HTTP Request)" node. - In the JSON Body field, you can edit the title and body expressions. For example, you could add the committer's name ({{$(Webhook).item.json.body.pusher.name}}) or a link back to the JIRA task. **2. Adapting to a Fixed Branching Strategy:** - If your team always creates pull requests against a single branch (e.g., develop), you can simplify the workflow. - In the "Request to create PR" node, change the base value in the JSON body from {{...}} to your static branch name: base: develop. - You can then remove the base branch logic from the "Commit Message Breakdown (Code)" node. **3. Modifying Notification Messages:** - The text sent to Slack and Notion is fully customizable. - Open any of the Slack or Notion nodes and edit the text fields. You can include any data from previous nodes, such as the PR URL ({{$(Request to create PR).item.json.body.html_url}}) or the repository name. **4. Adjusting the Commit Regex for Different Conventions:** - This is an advanced customization. If your team uses a different commit format (e.g., (DEV-123) instead of DEV-123), you can adjust the regex in the "Commit Message Breakdown (Code)" node to match your team's convention.
n8n$24.99Automate JIRA Ticket Assignment Using AI and Supabase
This workflow ensures JIRA issues are automatically assigned to the most suitable team member using AI and Supabase, preventing them from being unassigned for more than a week.
n8n$19.99Automate Employee Onboarding with Slack, Jira, and Google Workspace Integration
## Who is this for? This template is ideal for **HR teams, startup founders, operations leads, remote-first companies, and freelancers** managing onboarding manually or across multiple tools. Whether you're hiring your first intern or streamlining onboarding for dozens of new team members, this workflow automates the entire **trigger → task creation → onboarding delivery** process using no-code tools connected via n8n. --- ## What problem does this solve? Employee onboarding is often fragmented and error-prone, involving Jira tasks, Slack DMs, file sharing, and email templates spread across different apps. This workflow connects it all, letting you **create tasks, notify people, share folders, and message hires instantly** - right when they're marked as "Hired" in a Google Sheet or added to Slack. No more bouncing between 5 tabs. This is onboarding as a system. --- ## What this workflow does - Watches a Google Sheet (or Slack trigger) for new hires - Creates a Jira onboarding Epic with role-based subtasks - Generates a Google Drive folder and shares it with the new hire - Sends a personalized, HTML-formatted welcome email via Gmail - Posts a Slack message in the #onboarding channel + DM to the hire - Logs onboarding activity back to the Sheet (status, links, etc.) - Modular subtasks based on role/team (e.g., Dev vs Marketing vs Student) Expressions, fallback logic, and Slack-to-Jira user ID mapping built-in --- ## Setup 1. Create API credentials for: - Slack - Google Sheets - Google Drive - Jira Cloud - Gmail (API or SMTP) 2. Import the `.json` workflow into your n8n instance (Cloud or self-hosted) 3. Replace placeholder values (e.g., Project ID, Issue Type ID, folder path) 4. Customize onboarding messages, email HTML, and task logic 5. Test with included mock data (sample hire, Slack user, Jira user) 6. Activate your flow and start onboarding with one click --- ## Color-coded workflow notes This workflow uses **Innovatio's sticky note system** to guide you visually: - Green Notes → Main automation steps - Blue Notes → What to customize (IDs, prompts, expressions) - Yellow Notes → Optional logic and future upgrades - Gray Notes → Welcome + final "next steps" QA Every group includes pre-filled nodes, dynamic expressions, and mock outputs so you can test quickly and scale confidently. --- ## How to customize this workflow? - Swap Google Sheets for Airtable (better for teams or approvals) - Add 30/60/90-day check-ins via Google Calendar - Plug in OpenAI to generate onboarding subtasks by role - Auto-assign mentors or SlackBot reminders after 7 days - Push Sheet logs into Notion or your HR dashboard Need custom logic? Email me at **velebit@innovatio.design** --- ## Final notes This template was created by **Velebit from Innovatio** with modularity, scalability, and team experience in mind. All links included are official. No affiliate tracking, no sponsored content. A separate commercial license applies to the purchase via Gumroad, which includes extended rights, usage for client work, and scaling strategies.
n8n$24.99Automate Figma Version Tracking and Jira Issue Updates with n8n
Streamline your design and development workflow by automatically updating Jira issues with new Figma version details using n8n. This integration reduces manual updates and ensures synchronized information across teams.
n8n$4.99Manage Jira Issues with Natural Language via Telegram and GPT-4
## Manage Jira Issues with Natural Language via Telegram and GPT-4 ## Overview The Jira Agent is an AI-powered assistant that allows users to interact with Jira directly through the messaging platform Telegram. It leverages OpenAI's GPT-4 model to interpret natural language commands and perform various Jira-related actions. On Telegram, it enables users to create Jira stories by triggering a guided form when prompted with "create story". Additionally, it provides more extensive functionality, including creating, updating, searching, and transitioning Jira issues through natural language commands. ## How it works **Normal interaction** Using messages such as "Please give me all my issues." **Standardized process of creating stories:** 1. Message: create story 2. Open the Form that Telegram responds back to you 3. Fill in the essential story information in the form 4. The story automatically gets created in your backlog. ## Required Connections To use the Jira Agent effectively, users need access to: - A Telegram account, Telegram setup involves deploying the bot and starting a chat; story creation is triggered with a simple text command. - A connected Jira workspace - Permissions to create and modify Jira issues - Access to GPT-4 API-key Detailed configuration instructions are provided in the workflow. ## Setup Time <15 minutes ## Customizing this workflow - Try adding more details to the form for more complete Jira ticket creation. - Try connecting a Google Calendar node to plan your work.
n8n$14.99Automate Critical Error Alerts with Slack and Jira Integration
This workflow automates the detection and handling of critical errors in production environments by sending real-time alerts to Slack and creating Jira tickets for immediate resolution.
n8n$4.99Create an Intelligent IT Support Agent with Azure, Entra ID, and Jira
Develop an AI-powered IT support agent using Azure AI Search for knowledge management, Microsoft Entra ID for user administration, and Jira for issue tracking. This workflow enables efficient handling of IT queries and administrative tasks.
n8n$14.99Automate Support Email Sorting and Task Creation with AI and Jira
This n8n workflow automates the classification and routing of support emails using OpenAI, creates corresponding tasks in Jira, and sends autoresponses, streamlining your support process.
n8n$9.99
More integrations
Need a custom Jira workflow?
Our automation experts build tailored Jira integrations for your exact stack.
Request a Custom Workflow