Error monitor: AI-powered resolution [Context7, Supabase]
Ready for 3.0What this workflow does
This AI workflow has 18 nodes and runs when another workflow fails (error workflow). Along the way it connects Supabase, OpenRouter Chat Model and MCP Client.
How it runs
Trigger: When another workflow fails (error workflow).
- Get Workflow (n8n): get
- Get Execution (n8n): get (execution)
- Structure Error Data (Code): runs custom JavaScript code
- Find Workflow (Supabase): get many
- Workflow Exists? (If): checks a condition and branches into true / false
- Insert Error (Supabase): uses Supabase
- Create Workflow (Supabase): uses Supabase
- Update Statistics (Supabase): update
- Workflow Creation (Loop Over Items (Split in Batches)): loops over the items in batches
- AI Agent: runs an AI agent, with model: OpenRouter; 1 tool (Context)
…plus 5 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 (10)
- n8n
n8n-nodes-base.n8n - Supabase
n8n-nodes-base.supabase - If
n8n-nodes-base.if - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter - MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool - Code
n8n-nodes-base.code - Error Trigger
n8n-nodes-base.errorTrigger - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Send Email
n8n-nodes-base.emailSend
From the author
Never miss a workflow failure Automatically capture, analyze, and debug n8n workflow errors using Claude Sonnet 4 with real-time documentation lookup via Context7 MCP server. Why this works better Documentation-first AI analysis Context7 searches official n8n…