# Score and route incidents with Jev Classification, Google Sheets, Gmail, Telegram, and GPT-6-Luna

> A production incident report lands on a webhook and the right person is paged while everyone else is still reading the alert. This n8n workflow has Jev Classification score each incident for severity, logs the decision to Google Sheets, then routes it into five lanes: SEV1 declares the incident and pages the commander, SEV2 pages the on call engineer, SEV3 queues a service desk ticket, SEV4 waits in the backlog, and a low confidence score is held for the commander to confirm. A monthly cron turns the log into a counted trend brief for the engineering lead. Last updated: October 2026. Quick Overview This workflow takes production incident reports on the Incident Intake webhook, normalizes the id, service, impact, affected users and timestamps, and refuses to score a report with no service name or impact text. Usable reports go to Jev Score Incident Severity (jev-latest, confidence threshold 0.65), which returns a level, a score, a confidence and a needsReview flag that Route By Confiden

- **Domain**: `n8n-workflow-20451.n8n.io`
- **Provider**: n8n.io (https://n8n.io)
- **Kind**: workflow
- **Live-responds (last probe)**: None
- **Signed card**: False
- **Streaming**: False
- **Quality score**: 40%

## URLs
- Agent card: https://n8n.io/workflows/20451
- Page (HTML): https://agenstry.com/agents/n8n-workflow-20451.n8n.io
- Documentation: https://n8n.io/workflows/20451