Block 1 - Get Workflow
- Type / Role
- n8n-nodes-base.n8n - n8n
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
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. ![Screenshot 20251122 ...
n8n-nodes-base.n8n, n8n-nodes-base.supabase, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenrouter, @n8n/n8n-nodes-langchain.mcpclienttool, n8n-nodes-base.code, n8n-nodes-base.errortrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Kelsey Brown.
Original n8n.io sourceAutomatically capture, analyze, and debug n8n workflow errors using Claude Sonnet 4 with real-time documentation lookup via Context7 MCP server.
Documentation-first AI analysis
Context7 searches official n8n docs before diagnosing. Claude Sonnet 4 only responds after finding relevant documentation—no hallucinations.
Complete error intelligence
Every error stored in Supabase with full context: stack traces, execution data, workflow structure, AI analysis. Track patterns across all workflows.
Production-ready emails
Professional HTML with inline code snippets, proper formatting, and one-click execution links.
Root cause - Plain English explanation
Specific fix - Exact field names and values
Prevention tip - Avoid future errors
Execution link - One-click debug access
Statistics - Error frequency tracking
Setup: 15 minutes
Complete instructions with SQL script included in workflow sticky notes.
Activate: Settings → Error Workflow → Select this workflow
Reduce cost: Remove workflow_json and execution_data from prompt
Change output: Swap email node for Telegram/Slack/Discord—expressions provided in notes
Works with community nodes?
Yes. Context7 searches all n8n documentation.
Handles sensitive data?
Remove workflow_json and execution_data from prompt to exclude content.
Customizable design?
Yes. HTML template in "Build HTML" node is fully editable.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.
| Workflow | Error monitor: AI-powered resolution [Context7, Supabase] |
|---|---|
| Complexity | advanced |
| Nodes | 26 |
| Categories | Support |
| Author | Kelsey Brown |
| Published | 25 Nov 2025 |
Use the JSON export at /data/workflows/11219/11219.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
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. ![Screenshot 20251122 ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support use case.