Automation library · AI assistants

Triage Microsoft 365 incidents into Jira with OpenAI

Started by another system calling it, and works across Jira. It hands the judgement calls to OpenAI. 12 steps, 1 branch: a working afternoon to understand properly.

MediumCalls a model: OpenAI

12 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 2Model 1Logic 6Service 3

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

  1. 1Microsoft 365 TriggerWebhookStarts it
  2. 2Extract & ValidateCodeLogic
  3. 3Webhook ResponseRespond To WebhookStarts it
  4. 4Idempotency CheckCodeLogic
  5. 5AI Brain (GPT-4o-mini)Open AiModel
  6. 6Parse & EnrichCodeLogic
  7. 7Create Jira IncidentJiraService
  8. 8Build Enhanced CardCodeLogic
  9. 9P1/P2 CheckIfLogic
  10. 10Trigger PagerDutyPager DutyService
  11. 11Post to TeamsMicrosoft TeamsService
  12. 12Log SuccessCodeLogic

How it's built

Starts on
Another system calling it
Steps
12, with 1 branch
Size
Medium: a working afternoon
Connects to
Jira
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Jira account, and a key for OpenAI. 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 OpenAI. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 12 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 12 steps before you point it at anything that matters.