Skip to main content

Automate customer support issue resolution using AI text classifier

Workflow preview

Workflow preview
100%
Automate customer support issue resolution using AI text classifier preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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 da...

Best for

  • Ticket Management automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.scheduletrigger, n8n-nodes-base.jira, n8n-nodes-base.aggregate, n8n-nodes-base.set, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.slack

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jimleuk.

Original n8n.io source

1.1 Workflow description

Title
Automate customer support issue resolution using AI text classifier
Workflow name
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.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1

Block 2 - OpenAI Chat Model1

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1

Block 3 - OpenAI Chat Model3

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1

Block 4 - OpenAI Chat Model4

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1

Block 5 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 6 - Get Issue Comments

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 7 - Close Issue

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 8 - Send Reminder

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 9 - Join Comments

Type / Role
n8n-nodes-base.aggregate - aggregate
Config choices
Version 1

Block 10 - Add Autoclose Message

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 11 - Ask For Feedback Message

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 12 - Simplify Thread For AI

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 13 - Solution Found?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 14 - Reply to Issue

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 15 - Last Message is Not Bot

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 16 - Structured Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.2

Block 17 - Get Issue Metadata

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 18 - Notify Slack Channel

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.2

Block 19 - Close Issue2

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 20 - Get List of Unresolved Long Lived Issues

Type / Role
n8n-nodes-base.jira - jira
Config choices
Version 1

Block 21 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Execute Workflow

Type / Role
n8n-nodes-base.executeWorkflow - executeWorkflow
Config choices
Version 1.1

Block 23 - Execute Workflow Trigger

Type / Role
n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
Config choices
Version 1

Block 24 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 36 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Automate customer support issue resolution using AI text classifier
Complexity advanced
Nodes 36
Categories Ticket Management, AI Summarization
Author Jimleuk
Published 17 Oct 2024

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2468/2468.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automate customer support issue resolution using AI text classifier do?

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 da...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management, AI Summarization use case.