HumationHuman + Automation
Back to Catalog

Classify and convert GitHub issues to Jira tickets with OpenAI

Issam AGGOURIssam AGGOUR
34 views
2/3/2026
ExportData ExtractionActiveCampaignCSVAPI Automation
Official Page

AI-Powered GitHub Issue to Jira Ticket Automation

Bridge the gap between your development and project management workflows with this intelligent n8n template. This isn't just a simple sync; it uses an AI agent to analyze, classify, and intelligently route new GitHub issues into the correct Jira ticket type, saving you countless hours of manual triage.

🚀 Key Features

  • AI-Powered Issue Classification: Leverages an AI Agent (powered by OpenAI) to analyze the content of a new GitHub issue and determine its type (e.g., bug, task, improvement).
  • Intelligent Routing: Automatically creates the corresponding ticket type in Jira. Bugs in GitHub become Bugs in Jira; other issues become Tasks.
  • Seamless Integration: Triggers instantly when a new issue is created in your specified GitHub repository.
  • Rich Data Transfer: Migrates the issue title and body directly into the Jira ticket description for full context.
  • Structured AI Output: Uses a structured output parser to ensure the AI's classification is reliable and consistent.
  • Beginner-Friendly & Educational: The workflow is annotated with sticky notes, explaining each step of the process, making it a great tool for learning how to use AI in n8n.

⚙️ How It Works

The workflow is designed for clarity and power, moving from issue creation to ticket generation in four automated steps.

1. Trigger: New GitHub Issue

  • The GitHub Trigger node constantly listens for new issues being created in your designated repository. Once an issue is opened, the workflow springs into action.

2. Analyze: AI Classification

  • The issue's title and body are passed to an AI Agent.
  • Using a prompt designed for classification and an OpenAI Chat Model, the agent determines if the issue is a bug, task, or another category.
  • A Structured Output Parser ensures the AI returns clean, usable JSON data (e.g., {"type": "bug"}).

3. Route: Conditional Logic

  • An IF node checks the structured output from the AI agent.
  • If the type is "bug," the workflow proceeds down the "bug" path. Otherwise, it follows the default path for "tasks."

4. Create: Jira Ticket Generation

  • Depending on the route, the corresponding Jira node is activated.
  • A new ticket is created in your specified Jira project with the appropriate issue type (Bug or Task) and includes the full context from the original GitHub issue.

🛠️ Setup Steps & Credentials

To get this AI-powered workflow running, you'll need to configure a few credentials:

  1. GitHub:

    • Create a GitHub credential in n8n.
    • In the GitHub Trigger node, select your credential and specify the owner (your GitHub username or organization) and the repository you want to monitor.

  2. OpenAI:

    • Obtain an API Key from platform.openai.com.
    • Create an OpenAI credential in n8n.
    • In the OpenAI Chat Model node, select your newly created credential. You can also experiment with different models like gpt-4.1-mini for speed or gpt-4o for higher accuracy.

  3. Jira:

    • Create a Jira API token from your Atlassian account settings.
    • Create a Jira credential in n8n using your email, API token, and Atlassian domain.
    • In both the Create Jira Ticket (Bug) and Create Jira Ticket (Task) nodes, select your Jira credential and set your target project key.

💡 Customization & Learning

This workflow is a powerful starting point. Here are a few ways you can customize it and learn more:

  • Expand Classification: Modify the AI Agent's prompt and the IF node to handle more issue types, like improvement, documentation, or feature-request.
  • Add More Data: Enhance the Jira nodes to include labels, assignees, or priority levels based on the AI's output or the original GitHub issue's properties.
  • Swap AI Models: Try different language models by replacing the OpenAI node with one for Google Gemini, Anthropic Claude, or others supported by n8n.
  • Error Handling: Add a path for what to do if the AI fails to classify an issue, such as sending a notification to a Slack channel for manual review.

📋 Requirements

  • An active n8n instance.
  • GitHub API credentials.
  • OpenAI API credentials.
  • Jira API credentials.

Classify and Convert GitHub Issues to Jira Tickets with OpenAI

This n8n workflow automates the process of classifying new GitHub issues and converting them into structured Jira tickets using the power of OpenAI's language models. It provides a smart way to manage your open-source project contributions or internal bug reports by automatically routing them to the appropriate project management system.

What it does

This workflow streamlines your issue management by:

  1. Triggering on New GitHub Issues: It automatically starts whenever a new issue is opened in a specified GitHub repository.
  2. Filtering Issues (Implicit): The workflow is designed to process new issues. While there isn't an explicit "If" node for filtering issue types in the provided JSON, it's implied that the subsequent AI processing will handle the content of the issue.
  3. Classifying and Structuring with AI: It leverages an OpenAI AI Agent to read the GitHub issue's title and body, classify its intent, and extract relevant information to structure it for a Jira ticket. This involves:
    • Using an OpenAI Chat Model for natural language understanding and generation.
    • Employing a Simple Memory to maintain context during the AI's processing.
    • Utilizing a Structured Output Parser to ensure the AI's output is formatted correctly (e.g., as JSON) for easy consumption by the Jira node.
  4. Creating Jira Tickets: Based on the AI's structured output, it automatically creates a new ticket in Jira Software, populating fields like summary, description, and potentially other custom fields, ensuring consistency and saving manual effort.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (self-hosted or n8n Cloud).
  • GitHub Account: A GitHub account with access to the repository you want to monitor. You'll need to configure a GitHub Trigger credential in n8n.
  • OpenAI API Key: An OpenAI API key to access the OpenAI Chat Model. You'll need to configure an OpenAI credential in n8n.
  • Jira Software Account: A Jira Software account where you want to create tickets. You'll need to configure a Jira Software credential in n8n.

Setup/Usage

  1. Import the Workflow:
    • Download the workflow JSON provided.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON.
  2. Configure Credentials:
    • GitHub Trigger: Click on the "Github Trigger" node. Select or create a new GitHub API credential. You'll need to specify the repository and events (e.g., issues) to listen for.
    • OpenAI Chat Model: Click on the "OpenAI Chat Model" node (within the "AI Agent" cluster). Select or create a new OpenAI API credential using your OpenAI API Key.
    • Jira Software: Click on the "Jira Software" node. Select or create a new Jira Software API credential. This typically involves providing your Jira URL, email, and an API token.
  3. Customize AI Agent (Optional but Recommended):
    • Click on the "AI Agent" node. You might want to refine the prompt or instructions given to the AI to better suit your specific classification needs and Jira ticket structure.
    • Review the "Structured Output Parser" to ensure it matches the expected JSON format for your Jira ticket creation.
  4. Configure Jira Software Node:
    • Click on the "Jira Software" node.
    • Set the "Resource" to "Issue" and "Operation" to "Create".
    • Map the fields from the AI Agent's output to the corresponding Jira fields (e.g., Summary, Description, Project, Issue Type). You will likely use expressions (e.g., {{ $json.summary }}) to pull data from the AI's output.
  5. Activate the Workflow:
    • Once all credentials and configurations are set, click the "Activate" toggle in the top right corner of the n8n editor to turn the workflow on.

Now, whenever a new issue is opened in your configured GitHub repository, n8n will automatically process it, classify it with OpenAI, and create a corresponding ticket in Jira.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353