receive schedule events and list jira and label prioritize rewrite
Configured with Aggregate, Chain LLM, Jira, OpenAI Chat Model, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Integration
- Transform
- AI & models
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Get Open Tickets | Integration | Jira | getAll |
| Simplify Ticket | Transform | Edit Fields | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Structured Output Parser | Transform | Output Parser Structured | See node parameters |
| Label, Prioritize & Rewrite | AI & models | Chain LLM | See node parameters |
| Update Labels, Priority and Description | Integration | Jira | update |
| Get Recent Similar Issues Resolved | Integration | Jira | getAll |
| Loop Over Items | Routing | Loop Over Items | See node parameters |
| Issue Ref | Routing | No Op | See node parameters |
| Get Comments | Integration | Jira | issueComment / getAll |
| Simplify Comments | Transform | Edit Fields | See node parameters |
| Summarise Resolution | AI & models | Chain LLM | See node parameters |
| Simplify Issue | Transform | Edit Fields | See node parameters |
| Aggregate | Transform | Aggregate | See node parameters |
| OpenAI Chat Model1 | AI & models | OpenAI Chat Model | See node parameters |
| Return Fields | Transform | Edit Fields | See node parameters |
| Attempt to Resolve Issue | AI & models | Chain LLM | See node parameters |
| Aggregate1 | Transform | Aggregate | See node parameters |
| OpenAI Chat Model2 | AI & models | OpenAI Chat Model | See node parameters |
| Add Comment to Issue | Integration | Jira | issueComment |
| Mark as Seen | Transform | Remove Duplicates | removeItemsSeenInPreviousExecutions |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
jiraSoftwareCloudApiopenAiApi
Workflow notes
1. Get Open Tickets
1. Get Open Tickets
Read more about the Scheduled Trigger node
We can use a scheduled trigger to aggressively check for newly open tickets in our JIRA support queue. The "remove duplicates" node (ie. Mark as Seen) is used so that we don't process any issues more than once.
2. Automate Triaging of Ticket
2. Automate Triaging of Ticket
Read more about the Basic LLM node
New tickets always need to be properly labelled and prioritised but it's not always possible to get to update all incoming tickets if you're light on hands. Using an AI is a great use-case for triaging of tickets as its contextual understanding helps automates this step.
3. Attempt to Resolve Ticket Using Previously Resolved Issues
3. Attempt to Resolve Ticket Using Previously Resolved Issues
Learn more about the JIRA node
There are a number of approaches to also automate issue resolution. Here, we can search for similar tickets in the "Done" or resolved state and using the accepted answers of those tickets, provide context for an AI agent to suggest some ideas back to the user - best case, the fix is found and worst case, the user can add more debugging information through failed attempts.
4. Suggest a Resolution via Comment
4. Suggest a Resolution via Comment
Learn more about the JIRA node
Finally, we provide the context of past resolved tickets for the agent to suggest a few resolution ideas back to the user. Be sure to format the answer to match your company tone of voice as without, AI may sound quite technical and robotic!
Try It Out!
Try It Out!
This n8n template automates triaging of newly opened support tickets and issue resolution via JIRA.
If your organisation deals with a large number of support requests daily, automating triaging is a great use-case for introducing AI to your support teams. Extending the idea, we can also get AI to give a first attempt at resolving the issue intelligently.
How it works
- A scheduled trigger picks up newly opened JIRA support tickets from the queue and discards any seen before.
- An AI agent analyses the open ticket to add labels, priority on the seriousness of the issue and simplifies the description for better readability and understanding for human support.
- Next, the agent attempts to address and resolve the issue by finding similar issues (by tags) which have been resolved.
- Each similar issue has its comments analysed and summarised to identify the actual resolution and facts.
- These summarises are then used as context for the AI agent to suggest a fix to the open ticket.
How to use
- Simply connect your JIRA instance to the workflow and activate to start watching for open tickets. Depending on frequency, you may need to increase for decrease the intervals.
- Define labels to use in the agent's system prompt.
- Restrict to certain projects or issue types to suit your organisation.
Requirements
- JIRA for issue management and support portal
- OpenAI for LLM
Customising this workflow
- Not using JIRA? Try swapping out the nodes for Linear or your issue management system of choice.
- Try a different approach for issue resolution. You might want to try RAG approach where a knowledge base is used.
Need Help?
Join the Discord or ask in the Forum!
Happy Hacking!
receive schedule events and list jira and label prioritize rewrite
receive schedule events and list jira and label prioritize rewrite
Purpose and structure
This folder contains the receive schedule events and list jira and label prioritize rewrite workflow. Its executable nodes use aggregate, chainLlm, jira, lmChatOpenAi, noOp, outputParserStructured, removeDuplicates, scheduleTrigger, set, splitInBatches. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Schedule/0907_Schedule_Removeduplicates_Create_Scheduled.json MIT; preserve source notices.