Most-used Jira Trigger workflows
- 99problems (55 nodes)
- Assign Unassigned Jira Issues with Airtable and Openrouter Grok — n8n Jira Trigger workflow (41 nodes)
- Notify Customers of Resolved Jira Bugs with Gmail, Hubspot, Slack and Sheets (26 nodes)
- Qa Platform — Jira Story to Test Workflow — n8n Jira Trigger workflow (20 nodes)
- Enforce Pre-release Compliance with Jira, Monday.com, and Slack Alerts (15 nodes)
- Jira Retrospective — n8n Jira Trigger workflow (13 nodes)
- Turn New Jira Tickets Into Cloudcli AI Coding Sessions with Claude Code (13 nodes)
- Generate Lessons Learned Reports From Jira Epics with AI and Google Docs — n8n Jira Trigger workflow (13 nodes)
- Auto-resolve Jira Tickets with Github Copilot Using Port Context (13 nodes)
- Automatically Assign Jira Service Management Reporter From Forwarded Emails — n8n Jira Trigger workflow (11 nodes)
99problems. Uses agent, gmailTool, mattermostTool, googleSheets. Scheduled trigger; 55 nodes.
This workflow listens for Jira issue create/update events, finds unassigned issues in a target project, pulls team member data from Airtable plus each member’s open Jira workload, and uses an OpenRout
This workflow automatically handles every resolved Jira bug by verifying the fix, notifying the customer, updating HubSpot, commenting on the Jira issue, alerting the team on Slack, and logging everyt
QA Platform — Jira Story to Test Workflow. Uses jiraTrigger, postgres, httpRequest, slack. Webhook trigger; 20 nodes.
Description: Guarantee that only fully compliant stories and tasks make it into your release with this n8n automation template. The workflow monitors Jira for issue updates and link changes, validates
Jira Retrospective. Uses jira, agent, lmChatOpenAi, summarize. Event-driven trigger; 13 nodes.
Turn new Jira tickets into automated AI coding sessions. When a ticket is created, this workflow runs an AI coding agent (Claude Code, Cursor CLI, or Codex) on the task inside a CloudCLI cloud dev env
Jira users who want to *automate the generation of a Lessons Learned or Retrospective* report after an Epic is Done.
Coding agents can significantly speed up development, but crucial engineering context often gets lost in the process. This guide demonstrates how to use Port as a context lake in n8n workflows to auto
This workflow solves a common problem in Jira Service Management: when an email is forwarded to create a ticket, Jira often sets the forwarding system (e.g., support@yourcompany.com) as the reporter,
Sync Jira Issues With Subsequent Comments To Notion Database. Uses notion, stickyNote, jiraTrigger. Event-driven trigger; 10 nodes.
Sync Jira issues with subsequent comments to Notion database. Uses notion, stickyNote, jiraTrigger. Event-driven trigger; 10 nodes.
This workflow creates/updates/deletes a Notion database page when an issue is created/updated/deleted in Jira. Subsequent updates to the issue's title or status in Jira are updated in the Notion datab
Triggered via Jira webhook when a HIGH priority issue is created in your project Simultaneously sends alerts to Slack, Google Chat, and an escalation email to the configured manager(s) Configure the O
14 of 14 workflows in this view · Browse all →
FAQ
How many n8n Jira Trigger workflows are in the catalog?
14 n8n workflows in AutomationFlows currently use the Jira Trigger integration — triggers, actions, or both.
How do I connect Jira Trigger in n8n?
After importing the workflow JSON, n8n will prompt for Jira Trigger credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most Jira Trigger workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.