Skip to main content

Automate IT support: Convert emails to Jira tickets with AI resolution

Workflow preview

Workflow preview
100%
Automate IT support: Convert emails to Jira tickets with AI resolution preview
Open on n8n.io

Important notice

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

1. Workflow Overview

SmartSupport Flow: Auto Handle IT Requests from Email to JIRA with Slack notification Watch the demo video below: [![Watch the video](https://s3.ap southeast 1.amazonaws.com/automatewith.me/gmail t...

Best for

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

Tools used

n8n-nodes-base.gmailtrigger, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.filter, n8n-nodes-base.slack, n8n-nodes-base.sendgrid, n8n-nodes-base.gmail, @n8n/n8n-nodes-langchain.chainllm

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Automate IT support: Convert emails to Jira tickets with AI resolution
Workflow name
Automate IT support: Convert emails to Jira tickets with AI resolution

SmartSupport Flow: Auto-Handle IT Requests from Email to JIRA with Slack notification

Watch the demo video below:

Who’s it for

> This workflow is built for lean IT teams, office managers, and business operators who receive support requests via email and want to automate ticket creation, smart AI resolution advice, and seamless communication with both users and internal teams, all without lifting a finger.
If your team is tired of manually triaging inbox requests, this AI-powered flow will transform your support handling process.

How it works / What it does

  1. Trigger on New Email: Uses Gmail Trigger to detect new support request emails.
  2. Fetch Email Content: Retrieves the full message body and metadata.
  3. Check for Duplication: Skips processing if the email has already been handled (based on READ/UNREAD label).
  4. Mark as Read: Updates Gmail to mark the email as processed.
  5. Extract Structured Request: Uses the Support Request Reader Agent powered by OpenAI to extract:
    • Request title
    • Request description
    • Requested by
    • Department
    • Category and priority
  6. Create Jira Ticket: A main issue is created in Jira using the structured request.
  7. Generate AI-Based Solution: Invokes the IT Support Advisor Agent to propose resolution(s).
  8. Post Comment to Jira: Adds the suggested solution(s) to the issue as a comment.
  9. Notify IT Team: Sends the ticket and context to a Slack channel for visibility and action.
  10. (Optional) Send Email to Requester: Currently deactivated. Can be enabled to acknowledge receipt.

How to set up

  1. Gmail Integration
    • Connect Gmail in the “Gmail Trigger” and “Get Email Content” nodes.
  2. OpenAI Configuration
    • Use OpenAI API credentials in both the Reader and Advisor agent models.
  3. Jira Integration
    • Authenticate your Jira account.
    • Set project key and issue fields in the “Create Main Issue” node.
  4. Slack Notification
    • Configure Slack connection and select a target channel.
  5. Set up Jira, Slack, Email
    • Set your company Jira based URL, IT Support slack channel and IT Support email in the Edit Fields (Set) node
  6. (Optional) Email Acknowledgment
    • Provide SendGrid credentials and email template in the “Send email to requester” node if re-enabled.

Requirements

  • Gmail API access with appropriate permissions
  • OpenAI account with API access (for GPT-4 or GPT-3.5)
  • Jira instance with project and permission to create/comment on issues
  • Slack workspace and Webhook or OAuth setup
  • n8n instance running with all above integrations configured

How to customize the workflow

  • Enhance Email Deduplication: Adjust the deduplication logic to use message-id, threadId, or custom headers.
  • Expand Reader Agent: Configure the LLM to extract more details such as asset tags, urgency levels, or locations.
  • Tailor Advisor Agent: Adjust prompt to generate multiple solutions, troubleshooting guides, or internal references.
  • Routing by Department: Add logic to forward requests to different teams based on the request category or department.
  • Enable Email Acknowledgment: Activate and customize the email notification step to inform requesters that their issue is being handled.

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 - Check for New Emails

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

Block 2 - OpenAI Chat Model

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

Block 3 - Structured Output Parser

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

Block 4 - Check requester email

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

Block 5 - Send message to IT Support team

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

Block 6 - Send email to requester

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

Block 7 - Get Email Content

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 8 - OpenAI Chat Model1

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

Block 9 - Structured Output Parser1

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

Block 10 - IT Support Advisor Agent

Type / Role
@n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices
Version 1.7

Block 11 - Support Request Reader Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.8

Block 12 - Add resolution comment to tracking ticket

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

Block 13 - Mark a message as read

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 14 - Email has been processed?

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

Block 15 - Sticky Note

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

Block 16 - Setup Jira, Slack, Email

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

Block 17 - Sticky Note1

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

Block 18 - Sticky Note2

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

Block 19 - Submit JIRA request ticket

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

Block 20 - Sticky Note3

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

Block 21 - Sticky Note4

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

Block 22 - Sticky Note5

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

Block 23 - Sticky Note6

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

Block 24 - Sticky Note7

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

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

3. Summary Table

Workflow Automate IT support: Convert emails to Jira tickets with AI resolution
Complexity advanced
Nodes 25
Categories Ticket Management, AI Summarization
Author Trung Tran
Published 31 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6735/6735.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 IT support: Convert emails to Jira tickets with AI resolution do?

SmartSupport Flow: Auto Handle IT Requests from Email to JIRA with Slack notification Watch the demo video below: [![Watch the video](https://s3.ap southeast 1.amazonaws.com/automatewith.me/gmail t...

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.