👲 Monitor & debug n8n workflows with Claude AI assistant and MCP server
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs when an HTTP POST request hits its webhook URL. It uses only n8n's built-in nodes.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Route by Action (Switch): routes items into 3 branches
- Get Active Workflows (HTTP Request): calls an HTTP API
- Get Last Executions (HTTP Request): calls an HTTP API
- Get Executions Details (Status = Error) (HTTP Request): calls an HTTP API
- Split Active Executions (Split Out): splits a list into separate items
- Extract All Executions (Split Out): splits a list into separate items
- Details of Executions (Split Out): splits a list into separate items
- Active Workflows (Edit Fields (Set)): sets 5 fields: createdAt, updatedAt, id…
- Processing Audit (Code): runs custom JavaScript code
- Respond to Webhook: sends the response back to the webhook caller
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 (7)
- Switch
n8n-nodes-base.switch - Split Out
n8n-nodes-base.splitOut - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Webhook
n8n-nodes-base.webhook - Respond to Webhook
n8n-nodes-base.respondToWebhook - Code
n8n-nodes-base.code
From the author
Tags: AI Agent, MCP Server, n8n API, Monitoring, Debugging, Workflow Analytics, Automation Context Hi! I’m Samir — a Supply Chain Engineer and Data Scientist based in Paris, and founder of LogiGreen Consulting. This workflow is part of my latest project: an…