Automation library · Customer support

Ticket triage for Jira Service Management with Gemini

Started by another system calling it. It calls services over plain HTTP rather than through connectors. It hands the judgement calls to Gemini. 10 steps: a working afternoon to understand properly.

MediumCalls a model: Gemini

10 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Model 1Logic 6Service 2

The steps in the order they run, from what starts it.

  1. 1WebhookWebhookStarts it
  2. 2SET_SETUPSetLogic
  3. 3Build Payload for LLMCodeLogic
  4. 4AI Case TriageGoogle GeminiModel
  5. 5Normalize LLM OutputCodeLogic
  6. 6Build JIRA UpdateCodeLogic
  7. 7JIRA UpdateHttp RequestService
  8. 8On Update ResultCodeLogic
  9. 9JIRA Add CommentHttp RequestService
  10. 10Metrics GenerationCodeLogic

How it's built

Starts on
Another system calling it
Steps
10
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
Gemini

Questions

What does it need to run?

An n8n account, and a key for Gemini. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

Yes. It calls Gemini. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 10 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 10 steps before you point it at anything that matters.