Route and triage workflow errors with Gmail, Gemini and n8n API
Ready for 3.0What this workflow does
This AI workflow has 160 nodes and runs manually, when you click “Execute workflow” (plus 15 other triggers). Along the way it connects Google Gemini Chat Model, Gmail, Telegram and Slack and 2 more.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 15 other triggers).
- Create Config Table (Data table): create (table)
- Get Config For Form (Data table): get
- Get All Workflows (n8n): uses n8n
- Get Recent Incidents (Data table): get
- Get Config for Guide (Data table): get
- Build Sim Payload (Edit Fields (Set)): sets 15 fields: scenario, safe_scenario, raw_wf_id…
- Ingest Error Payload (Edit Fields (Set)): sets 8 fields: raw_wf_id, raw_wf_name, raw_ex_id…
- Check Config Body (If): checks a condition and branches into true / false
- Parse Workflow IDs (Edit Fields (Set)): sets 1 field: workflow_ids
- Parse Disconnect IDs (Edit Fields (Set)): sets 1 field: workflow_id
…plus 132 more steps. 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 (24)
- Manual Trigger
n8n-nodes-base.manualTrigger - Data table
n8n-nodes-base.dataTable - If
n8n-nodes-base.if - Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - Respond to Webhook
n8n-nodes-base.respondToWebhook - n8n
n8n-nodes-base.n8n - Aggregate
n8n-nodes-base.aggregate - Split Out
n8n-nodes-base.splitOut - Error Trigger
n8n-nodes-base.errorTrigger - Crypto
n8n-nodes-base.crypto - Switch
n8n-nodes-base.switch - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Stop and Error
n8n-nodes-base.stopAndError - Gmail
n8n-nodes-base.gmail - Telegram
n8n-nodes-base.telegram - Slack
n8n-nodes-base.slack - Discord
n8n-nodes-base.discord - Microsoft Teams
n8n-nodes-base.microsoftTeams - HTTP Request
n8n-nodes-base.httpRequest - Limit
n8n-nodes-base.limit - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Quick Overview This workflow turns n8n into a centralized error handler with a browser-based dashboard, storing incidents in n8n Data Tables, optionally diagnosing failures with Google Gemini, notifying via Gmail (and optionally…