HumationHuman + Automation
Back to Catalog

GitHub to Jira bug sync with GPT-4o analysis & team alerts

Shelly-Ann DavyShelly-Ann Davy
175 views
2/3/2026
Cloud StorageGoogle DriveAutomationAzure Blob StorageFile Transfer
Official Page

Automate Bug Reports: GitHub Issues → AI Analysis → Jira Tickets with Slack & Discord Alerts

Automatically convert GitHub issues into analyzed Jira tickets with AI-powered severity detection, developer assignment, and instant team alerts.

Overview

This workflow captures GitHub issues in real-time, analyzes them with GPT-4o for severity and categorization, creates enriched Jira tickets, assigns the right developers, and notifies your team across Slack and Discord—all automatically.

Features

  • AI-Powered Triage: GPT-4o analyzes bug severity, category, root cause, and generates reproduction steps
  • Smart Assignment: Automatically assigns developers based on mentioned files and issue context
  • Two-Way Sync: Posts Jira ticket links back to GitHub issues
  • Multi-Channel Alerts: Rich notifications in Slack and Discord with action buttons
  • Time Savings: Eliminates 15-30 minutes of manual triage per bug
  • Customizable Routing: Easy developer mapping and priority rules

What Gets Created

Jira Ticket:

  • Original GitHub issue details with reporter info
  • AI severity assessment and categorization
  • Reproduction steps and root cause analysis
  • Estimated completion time
  • Automatic labeling and priority assignment

GitHub Comment:

  • Jira ticket link
  • AI analysis summary
  • Assigned developer and estimated time

Team Notifications:

  • Severity badges and quick-access buttons
  • Developer assignment and root cause summary
  • Color-coded priority indicators

Use Cases

  • Development teams managing 10+ bugs per week
  • Open source projects handling community reports
  • DevOps teams tracking infrastructure issues
  • QA teams coordinating with developers
  • Product teams monitoring user-reported bugs

Setup Requirements

Required:

  • GitHub repository with admin access
  • Jira Software workspace
  • OpenAI API key (GPT-4o access)
  • Slack workspace OR Discord server

Customization Needed:

  1. Update developer email mappings in "Parse GPT Response & Map Data" node
  2. Replace YOUR_JIRA_PROJECT_KEY with your project key
  3. Update Slack channel name (default: dev-alerts)
  4. Replace YOUR_DISCORD_WEBHOOK_URL with your webhook
  5. Change your-company.atlassian.net to your Jira URL

Setup Time: 15-20 minutes

Configuration Steps

  1. Import workflow JSON into n8n
  2. Add credentials: GitHub OAuth2, Jira API, OpenAI API, Slack, Discord
  3. Configure GitHub webhook in repository settings
  4. Customize developer mappings and project settings
  5. Test with sample GitHub issue
  6. Activate workflow

Expected Results

  • 90% faster bug triage (20 min → 2 min per issue)
  • 100% consistency in bug analysis
  • Zero missed notifications
  • Better developer allocation
  • Improved bug documentation

Tags

GitHub, Jira, AI, GPT-4, Bug Tracking, DevOps, Automation, Slack, Discord, Issue Management, Development, Project Management, OpenAI, Webhook, Team Collaboration

GitHub to Jira Bug Sync with GPT-4o Analysis & Team Alerts

This n8n workflow automates the process of creating Jira bug tickets and notifying teams in Slack and Discord whenever a new GitHub issue is opened with the "bug" label. It leverages OpenAI's GPT-4o to analyze the GitHub issue description and enrich the Jira ticket with a summarized bug report and suggested severity.

What it does

  1. Listens for GitHub Issues: Triggers whenever a new issue is opened in a specified GitHub repository.
  2. Filters for "bug" label: Checks if the new GitHub issue has the "bug" label.
  3. Analyzes with OpenAI (GPT-4o): If it's a bug, it sends the issue title and description to OpenAI's GPT-4o model to:
    • Generate a concise summary of the bug.
    • Suggest a severity level (e.g., Low, Medium, High, Critical) based on the description.
    • Extract key information relevant for a bug report.
  4. Creates Jira Bug Ticket: Uses the analyzed information to create a new bug ticket in Jira, populating fields like summary, description, and suggested severity.
  5. Notifies Slack Channel: Posts a detailed alert to a designated Slack channel, including a link to the new Jira ticket and the GitHub issue.
  6. Notifies Discord Channel: Posts a similar alert to a Discord channel, ensuring wider team visibility.
  7. Responds to Webhook: Provides a response to the initial webhook trigger, indicating the successful processing of the issue.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • GitHub Account: Configured GitHub credentials in n8n with access to the target repository.
  • Jira Software Account: Configured Jira Software credentials in n8n with permissions to create issues in the target project.
  • OpenAI API Key: An OpenAI API key with access to GPT-4o.
  • Slack Account: Configured Slack credentials in n8n with permission to post messages to the target channel.
  • Discord Account: Configured Discord credentials in n8n with permission to post messages to the target channel.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • GitHub Node (ID: 16): Select or create your GitHub credential. Configure it to listen for Issue events in your desired repository.
    • OpenAI Node (ID: 1250): Select or create your OpenAI credential using your API key.
    • Jira Software Node (ID: 77): Select or create your Jira credential. Configure the "Create" operation to create a "Bug" issue type in your desired project. Map the fields using expressions from the OpenAI output (e.g., summary, description, and suggested severity).
    • Slack Node (ID: 40): Select or create your Slack credential. Configure it to post messages to your team's alert channel. Customize the message to include links to the GitHub issue and the newly created Jira ticket.
    • Discord Node (ID: 60): Select or create your Discord credential. Configure it to post messages to your team's alert channel. Customize the message similarly to Slack.
  3. Activate the Workflow: Toggle the workflow to "Active" in n8n.

Now, whenever a new issue with the "bug" label is opened in your configured GitHub repository, this workflow will automatically create a Jira ticket, analyze the bug with AI, and notify your teams.

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

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942