n8n Incident Routing: Jev Severity Scoring to Sheets, Gmail & Telegram

Automatically score incident severity and route the right alerts with Jev—then log everything in Google Sheets

This n8n Incident Routing workflow takes production incident reports from your Incident Intake webhook, uses Jev Severity Scoring to classify severity with confidence, records the decision in Google Sheets, and routes each incident into the correct escalation lane—so the right person gets paged while others are still reading.

What this workflow does

• Receives incident reports via a POST request to the jev-c2-incident-intake webhook.
• Normalizes incident fields (including incident_id, service, impact_text, affected_users, and timestamps) and refuses to score reports with no service name or no impact text.
• Scores severity with Jev (jev-latest, confidence threshold 0.65) to produce: a level, a score, a confidence value, and a needsReview flag.
• Routes into five lanes via Route By Confidence And Severity:
  • SEV1: declares the incident and pages the commander
  • SEV2: pages the on-call engineer
  • SEV3: queues a service desk ticket
  • SEV4: holds in the backlog
  • Low confidence: retains for commander confirmation
• Logs every decision by appending the full record to the Incident Severity tab in Google Sheets before paging/emailing anyone.
• Runs monthly trends: a monthly cron uses gpt-6-luna to generate a counted severity trend brief for the engineering lead.

Use cases

• Centralize production incident intake and standardize severity scoring across services.
• Reduce alert fatigue by paging only on SEV1/SEV2, while handling lower levels via backlog/tickets.
• Provide an audit trail in Google Sheets and track trends with a monthly summary.

Technical details

• n8n nodes used: webhook, set, if, switch, gmail, telegram
• Routing is driven by confidence + Jev severity (including needsReview)

Last updated: October 2026.