Skip to main content

Daily Jira ticket summarizer using GPT-5 and Jira API

Workflow preview

Workflow preview
100%
Daily Jira ticket summarizer using GPT-5 and Jira API preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Who is this for? This workflow is perfect for: Support teams and customer service departments managing Jira tickets Team leads and managers who need daily visibility into ticket resolution progress...

Best for

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

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.merge, n8n-nodes-base.aggregate, n8n-nodes-base.jira, n8n-nodes-base.splitout, n8n-nodes-base.splitinbatches, @n8n/n8n-nodes-langchain.chainllm, n8n-nodes-base.set

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Daily Jira ticket summarizer using GPT-5 and Jira API
Workflow name
Daily Jira ticket summarizer using GPT-5 and Jira API

Who is this for?

This workflow is perfect for:

  • Support teams and customer service departments managing Jira tickets
  • Team leads and managers who need daily visibility into ticket resolution progress
  • Organizations wanting to automate ticket reporting and communication
  • IT departments seeking to streamline support ticket summarization and tracking

What problem is this workflow solving?

Manual ticket review and reporting is time-consuming and often lacks comprehensive analysis. This workflow solves those issues by:

  • Automating daily ticket analysis by fetching, analyzing, and summarizing all tickets created each day
  • Providing intelligent summaries using AI to extract key insights from ticket descriptions, comments, and resolutions
  • Streamlining communication by automatically sending formatted daily reports to stakeholders
  • Saving time by eliminating manual ticket review and report generation

What this workflow does

This workflow automatically fetches daily Jira tickets, analyzes them with AI, and sends comprehensive summaries via email to keep your team informed about support activities.

Step by step:

  1. Schedule Trigger runs the workflow automatically at your chosen interval (or manual trigger for testing)
  2. Set Project Key defines the Jira project to monitor (default: SUP project)
  3. Get All Tickets from the specified project created today
  4. Split Out extracts individual ticket data including key, summary, and description
  5. Loop Tickets processes each ticket individually through batch processing
  6. Get Comments from Ticket retrieves all comments and conversations for complete context
  7. Merge combines ticket data with associated comments for comprehensive analysis
  8. Ticket Summarizer (AI Agent) uses OpenAI GPT-5 to generate professional summaries and proposed solutions
  9. Set Output structures the AI analysis into standardized JSON format
  10. Aggregate collects all processed ticket summaries into a single dataset
  11. Format Body creates a readable email format with direct Jira ticket links
  12. Send Ticket Summaries delivers the daily report via Gmail

How to set up

  1. Connect your Jira account by adding your Jira Software Cloud API credentials to the Jira nodes
  2. Add your OpenAI API key to the OpenAI Chat Model node for AI-powered ticket analysis
  3. Configure Gmail credentials for the Send Ticket Summaries node to deliver reports
  4. Update the recipient email in the "Send Ticket Summaries" node to your desired recipient
  5. Adjust the project key in the "Set Project Key" node to match your Jira project identifier
  6. Configure the schedule trigger to run daily at your preferred time for automatic reporting
  7. Customize the JQL query in Jira nodes to filter tickets based on your specific requirements
  8. Test the workflow using the manual trigger to ensure proper ticket fetching and AI analysis
  9. Review email formatting in the "Format Body" node and adjust as needed for your reporting style

How to customize this workflow to your needs

  • Modify AI prompts: customize the ticket analysis prompt in the "Ticket Summarizer" node to focus on specific aspects like priority, resolution time, or customer impact
  • Adjust ticket filters: change the JQL queries to filter by status, priority, assignee, or custom date ranges beyond "today"
  • Add more data points: include additional ticket fields like priority, status, assignee, or custom fields in the analysis
  • Customize email format: modify the "Format Body" node to change the report structure, add charts, or include additional formatting
  • Set up different schedules: create multiple versions for different reporting frequencies (hourly, weekly, monthly)

Need help customizing?

Contact me for consulting and support:
📧 [email protected]

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 - When clicking ‘Test workflow’

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

Block 2 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.1

Block 3 - Aggregate

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

Block 4 - Merge5

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.1

Block 5 - Get All Tickets Today

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

Block 6 - Get All Tickets

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

Block 7 - Split Out

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

Block 8 - Loop Tickets

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 9 - Ticket Summarizer

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

Block 10 - Get Comments from Ticket

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

Block 11 - Set Output

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

Block 12 - Format Body

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 13 - Send Ticket Summaries

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

Block 14 - OpenAI Chat Model

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

Block 15 - Structured Output Parser

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

Block 16 - Set Project Key

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

Block 17 - Get All Tickets Without Filter

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

Block 18 - Sticky Note1

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

Block 19 - Sticky Note

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

Block 20 - Sticky Note2

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 Note3

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 - Schedule Trigger

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

3. Summary Table

Workflow Daily Jira ticket summarizer using GPT-5 and Jira API
Complexity advanced
Nodes 24
Categories Ticket Management, AI Summarization
Author Billy Christi
Published 01 Sept 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/8103/8103.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 Daily Jira ticket summarizer using GPT-5 and Jira API do?

Who is this for? This workflow is perfect for: Support teams and customer service departments managing Jira tickets Team leads and managers who need daily visibility into ticket resolution progress...

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.