Triage Microsoft 365 incidents into Jira with GPT-4o-mini, PagerDuty and Teams
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 12 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects OpenAI, Jira Software, PagerDuty and Microsoft Teams.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Extract & Validate (Code): runs custom JavaScript code
- Webhook Response (Respond to Webhook): sends the response back to the webhook caller
- Idempotency Check (Code): runs custom JavaScript code
- AI Brain (GPT-4o-mini) (OpenAI): uses OpenAI
- Parse & Enrich (Code): runs custom JavaScript code
- Create Jira Incident (Jira Software): uses Jira Software
- Build Enhanced Card (Code): runs custom JavaScript code
- P1/P2 Check (If): checks a condition and branches into true / false
- Trigger PagerDuty (PagerDuty): create (incident)
- Post to Teams (Microsoft Teams): work with message
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Webhook
n8n-nodes-base.webhook - Respond to Webhook
n8n-nodes-base.respondToWebhook - Code
n8n-nodes-base.code - OpenAI
@n8n/n8n-nodes-langchain.openAi - Jira Software
n8n-nodes-base.jira - If
n8n-nodes-base.if - PagerDuty
n8n-nodes-base.pagerDuty - Microsoft Teams
n8n-nodes-base.microsoftTeams
From the author
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…