Jira service desk triage with Gemini
Gemini proposes severity and component for new tickets. This n8n template starts from a Jira Service Management webhook when a ticket is created. Google Gemini or Gemma proposes a severity, a component, guidance and the missing information. When the model's confidence reaches a set threshold, the workflow updates priority, component and labels on the ticket. It also posts an internal audit comment with three next steps, the missing information and the justifications with their confidence. It calls the Jira API through a bot user with HTTP Basic Auth. It is for service desk teams on Jira Service Management.
Steps
- Trigger: Webhook triggers on ticket creation
- Loads domain rules
Priority policy, components, guidance templates. - Sets confidence threshold and triage label
- Builds a payload with ticket and domain context
- Gemini proposes severity, component and guidanceGoogle Gemini
- Output normalized for safe automation
- Updates fields if confidence passes the thresholdJira Service Management
Priority, component, labels. - Posts an internal audit commentJira Service Management
3 next steps, missing info, justifications. - Output: Captures metrics for reporting
Applied changes, confidence, API statuses.
Limits
- Needs a dedicated Jira bot user with an API token.
- Fields change only when the confidence threshold is met.
What it does well
- Leaves an internal audit comment with its justifications.
- The page says it runs on cloud or self-hosted n8n.
Before you import
Needs Jira Service Management API access, a Google Gemini or Gemma credential and an HTTP Basic Auth credential for a dedicated bot user with an API token. The page says the import works on cloud or self-hosted n8n.
Similar templates
Contact form spam and enquiry sorting
Also for customer support, 6 steps.
Contact form triage and auto-replies
Also for customer support, 8 steps.
Support tickets to Jira with Gemini
Also for customer support, 8 steps.
Sort incoming requests
Other templates that do this task.