Triage Microsoft 365 incidents into Jira with GPT-4o-mini, PagerDuty and Teams

Manual incident triage kills your MTTR. This workflow automates the first response so your engineers get actionable tickets instead of raw alerts.

This workflow takes unstructured incident reports from Microsoft 365 and turns them into structured Jira tickets with severity, affected systems, root cause hypothesis, and recommended actions. It analyzes impact, routes critical failures to PagerDuty, and posts clear summaries to Teams.

---

How it works The workflow operates in four synchronized stages:

The workflow runs in four stages:

1. Reliable ingestion: Webhook triggers and returns 202 Accepted immediately. This prevents the source system from timing out or sending duplicate retries while the AI processes the data. Security and deduplication:

2. Validation: Checks webhook signatures and sanitizes input to block prompt injection. Idempotency: Compares incident ID against a 1,000-event rolling window in staticData. No duplicate tickets for the same issue.

3. AI analysis: GPT-4o-mini analyzes the report. Extracts a title, assigns severity (P1-P4), identifies affected systems, generates root cause hypothesis and next steps. The Parse & Enrich node catches malformed AI output and fails gracefully into a "Manual Review" state. Orchestrated response: