{"product_id":"n8n-incident-routing-jev-severity-scoring-to-sheets-gmail-telegram","title":"n8n Incident Routing: Jev Severity Scoring to Sheets, Gmail \u0026 Telegram","description":"\u003ch3\u003eAutomatically score incident severity and route the right alerts with Jev—then log everything in Google Sheets\u003c\/h3\u003e\n\u003cp\u003eThis \u003cstrong\u003en8n Incident Routing\u003c\/strong\u003e workflow takes production incident reports from your \u003cem\u003eIncident Intake\u003c\/em\u003e webhook, uses \u003cstrong\u003eJev Severity Scoring\u003c\/strong\u003e to classify severity with confidence, records the decision in \u003cstrong\u003eGoogle Sheets\u003c\/strong\u003e, and routes each incident into the correct escalation lane—so the right person gets paged while others are still reading.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eReceives incident reports\u003c\/strong\u003e via a POST request to the \u003ccode\u003ejev-c2-incident-intake\u003c\/code\u003e webhook.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNormalizes incident fields\u003c\/strong\u003e (including incident_id, service, impact_text, affected_users, and timestamps) and \u003cstrong\u003erefuses to score\u003c\/strong\u003e reports with \u003cstrong\u003eno service name\u003c\/strong\u003e or \u003cstrong\u003eno impact text\u003c\/strong\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eScores severity with Jev\u003c\/strong\u003e (jev-latest, \u003cstrong\u003econfidence threshold 0.65\u003c\/strong\u003e) to produce: a level, a score, a confidence value, and a \u003ccode\u003eneedsReview\u003c\/code\u003e flag.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRoutes into five lanes\u003c\/strong\u003e via \u003cstrong\u003eRoute By Confidence And Severity\u003c\/strong\u003e:\n    \u003cul\u003e\n      \u003cli\u003e\n\u003cstrong\u003eSEV1\u003c\/strong\u003e: declares the incident and pages the commander\u003c\/li\u003e\n      \u003cli\u003e\n\u003cstrong\u003eSEV2\u003c\/strong\u003e: pages the on-call engineer\u003c\/li\u003e\n      \u003cli\u003e\n\u003cstrong\u003eSEV3\u003c\/strong\u003e: queues a service desk ticket\u003c\/li\u003e\n      \u003cli\u003e\n\u003cstrong\u003eSEV4\u003c\/strong\u003e: holds in the backlog\u003c\/li\u003e\n      \u003cli\u003e\n\u003cstrong\u003eLow confidence\u003c\/strong\u003e: retains for commander confirmation\u003c\/li\u003e\n    \u003c\/ul\u003e\n  \u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eLogs every decision\u003c\/strong\u003e by appending the full record to the \u003cstrong\u003eIncident Severity\u003c\/strong\u003e tab in Google Sheets before paging\/emailing anyone.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRuns monthly trends\u003c\/strong\u003e: a monthly cron uses \u003cstrong\u003egpt-6-luna\u003c\/strong\u003e to generate a counted severity trend brief for the engineering lead.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eCentralize production incident intake and \u003cstrong\u003estandardize severity scoring\u003c\/strong\u003e across services.\u003c\/li\u003e\n  \u003cli\u003eReduce alert fatigue by paging only on \u003cstrong\u003eSEV1\/SEV2\u003c\/strong\u003e, while handling lower levels via backlog\/tickets.\u003c\/li\u003e\n  \u003cli\u003eProvide an audit trail in \u003cstrong\u003eGoogle Sheets\u003c\/strong\u003e and track trends with a monthly summary.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003en8n nodes used: \u003cstrong\u003ewebhook\u003c\/strong\u003e, \u003cstrong\u003eset\u003c\/strong\u003e, \u003cstrong\u003eif\u003c\/strong\u003e, \u003cstrong\u003eswitch\u003c\/strong\u003e, \u003cstrong\u003egmail\u003c\/strong\u003e, \u003cstrong\u003etelegram\u003c\/strong\u003e\n\u003c\/li\u003e\n  \u003cli\u003eRouting is driven by \u003cstrong\u003econfidence + Jev severity\u003c\/strong\u003e (including \u003ccode\u003eneedsReview\u003c\/code\u003e)\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003cp\u003e\u003cem\u003eLast updated: October 2026.\u003c\/em\u003e\u003c\/p\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":46192875831475,"sku":"N8N-20451","price":33.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/kz5SQjhMZ1-T-lZtJ2K_0UYX9g1I.png?v=1791538007","url":"https:\/\/buyflowscripts.com\/products\/n8n-incident-routing-jev-severity-scoring-to-sheets-gmail-telegram","provider":"N8N Commerce","version":"1.0","type":"link"}