n8n AI-Powered Bug Triage: Webhook Ingests Reports, GPT-4 Analyzes, Creates Jira Issues, and Alerts Slack

External system POSTs bug suspicion via Webhook → OpenAI (GPT-4) analyzes priority and category → Switch routes to High/Medium/Low Jira creation nodes → Slack pushes to different channels by priority

Who

Ops, QA, or developers who need to automatically turn external bug signals into Jira tickets with QA Slack alerts

You get

Bug reports are AI-analyzed and automatically create labeled Jira Bugs, with Slack notifications routed by priority

You need

n8n · jira · slack

Steps

1. Configure the Webhook trigger node

   After importing the template JSON into n8n, open the Webhook Trigger node. Set Method to POST. Use the value from workflow.json as the source of truth: webhookId and parameters.path are both advanced-bug-triage (description Step 1 separately lists bug-suspicion, which is inconsistent—verify against your import). Copy the generated Webhook URL for your external system to call.

2. Add OpenAI credentials and configure the AI analysis node

   Open the AI Bug Analysis (OpenAI) node and select your OpenAI credentials. The source sticky note indicates GPT-4 is used, but the workflow.json parameters for this node only contain options and requestOptions, with no explicit model setting and no published system/user prompt; the description only notes you can modify prompts, map input fields, or adjust model parameters as needed.

3. Add Jira credentials and configure creation nodes

   Open the Create High Jira, Create Medium Jira, and Create Low Jira nodes and select your Jira credentials. Ensure the credentials have access to project APP (or your custom project) and permission to create Bug issue types. Each node uses summary expression =[{{$json.priority}}] {{$json.summary}} and additionalFields.labels containing ai-triaged plus the lowercased category ={{$json.category.toLowerCase()}}. The Priority Switch routes by value1 ={{$json.priority}} with dataType string and fallbackOutput 1 (Medium branch) to the three Jira nodes.

4. Add Slack credentials and configure notification nodes

   Open the Slack Alert (High) and Slack Alert (Normal) nodes, select your Slack Bot credentials, and ensure the bot is invited to the target channels. High node channel: qa-alerts-high. Normal node channel: qa-general. Create High Jira connects to Slack Alert (High); Create Medium Jira and Create Low Jira both connect to Slack Alert (Normal).

   Execution prompt · Source text。Slack Alert (High) node text field (n8n expression)

   Copy prompt

   =HIGH PRIORITY BUG DETECTED
   
   Issue: {{$json.key}} - {{$json.fields.summary}}
   Link: {{$json.self}}

   Execution prompt · Source text。Slack Alert (Normal) node text field (n8n expression)

   Copy prompt

   =New Bug Reported: {{$json.key}}

5. Test the Webhook

   Send a POST request to the Webhook URL with a test payload: {"title": "Login button unresponsive"}. Observe whether the workflow executes through Jira creation and Slack notification. If Jira fields are empty, verify the payload includes a title field; if Slack shows undefined, add a Debug node after Jira to inspect output.

6. Activate the workflow

   Enable the Active toggle in n8n so the workflow continuously listens for Webhook requests.

You are setting up an n8n automation workflow: an external system submits bug suspicions via Webhook, GPT-4 analyzes priority and category, Jira Bugs with labels are created automatically, and Slack notifications are sent to different channels by priority. First confirm you have credentials for n8n, Jira (create Bug permission in project APP), OpenAI API, and Slack Bot Token. Then configure the Webhook path, select credentials, set channel names, and send a test POST to verify end-to-end connectivity. Note: the source has two inconsistent Webhook paths; follow your imported workflow.json as the source of truth. The OpenAI node prompt needs to be supplied by you.