n8n Error Triage Workflow: Gmail Alerts + Gemini Diagnosis

Turn n8n failures into actionable alerts—plus optional Google Gemini diagnosis

This n8n Error Triage Workflow acts as a centralized error handler with a browser-based dashboard. When connected workflows fail, it fingerprints recurring errors, applies severity escalation and exponential backoff, logs incidents in n8n Data Tables, and can optionally use Google Gemini to produce a JSON diagnostic summary. Notifications are sent via Gmail and optional channels (Slack/Telegram/Discord/Microsoft Teams or webhooks), with one-click retry and mute actions.

What this workflow does

• Initial setup (manual trigger): creates n8n Data Tables for configuration, error fingerprints, and incident history. If missing, it seeds a default config row.
• Dashboard & configuration UI: serves a Settings web interface via webhook endpoints, reads current configuration from Data Tables, and saves updates through a POST webhook (with validation feedback).
• Connect workflows: provides a “Connect” web UI that lists workflows using the n8n API, letting you bulk attach/detach this workflow as the error workflow.
• Error triage on failure: normalizes the error payload, fingerprints recurring errors, checks mute state, and escalates severity with exponential backoff based on stored configuration.
• Optional Gemini diagnosis: calls Google Gemini to generate a JSON diagnostic summary and retry/severity guidance.
• Multi-channel alerting & logging: sends formatted alerts via Gmail and any enabled channels (Telegram, Slack, Discord, Microsoft Teams, or HTTP webhook), then logs the incident.

Use cases

• SaaS operators who want single-pane-of-glass n8n error alerts with history and escalation.
• Automation engineers needing recurring error fingerprinting and controlled retry behavior.
• Teams that want faster debugging via Google Gemini diagnostic summaries triggered by workflow failures.

Technical details

• Integrations/nodes: if, n8n, set, gmail, limit, slack (plus optional channels described above via workflow capabilities).
• Storage: n8n Data Tables for configuration, fingerprints, and incident history.
• Interfaces: webhook-driven Settings UI, Connect UI, and failure-trigger triage handling.