n8n-debugger

Diagnose and fix broken n8n workflows through structured debugging steps.

4|1|Updated Nov 2, 2025

Search Tags:#debugging #credentials #n8n #errors #workflows #expressions #http-requests

Ready to run

npx skills add https://github.com/Wolfe-Jam/faf-skills --skill n8n-debugger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: n8n-debugger
Source: https://github.com/Wolfe-Jam/faf-skills/tree/main/skills/n8n-debugger
Command: npx skills add https://github.com/Wolfe-Jam/faf-skills --skill n8n-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps diagnose and fix broken n8n workflows by guiding through errors, execution logs, and systematic debugging.

Core Features & Use Cases

Systematic debugging approach for identifying, isolating, and resolving issues in n8n workflows.
Common error types & fixes including Expression Errors, HTTP Request Errors, Data Flow Issues, and Credential Problems with practical remedies.
Debugging tools & techniques such as enabling detailed logs, using Set nodes for inspection, and testing with minimal data to reproduce issues.

Quick Start

Activate this skill when a workflow error occurs and guide you through identifying, isolating, and patching the failing node.

Frequently Asked Questions about n8n-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug a broken n8n workflow?▼

Debugging n8n workflows involves systematically identifying and isolating failing nodes, inspecting execution logs, and resolving expression or data flow errors to restore normal operation.

Why does my n8n HTTP request node keep failing?▼

n8n HTTP request errors often stem from incorrect expressions, malformed payloads, or expired credentials. Diagnose the failure by testing with minimal data to reproduce the issue and reviewing detailed execution logs to apply targeted fixes.

How do I resolve credential problems in n8n workflows?▼

Resolve n8n credential problems by verifying authentication configurations within your nodes, checking for expired tokens, and ensuring the credential type matches the target API's requirements to prevent failed executions.

Can I use this debugging approach for self-hosted and serverless n8n setups?▼

Yes, this debugging approach applies to diverse n8n environments, including both self-hosted and serverless setups. It provides structured steps to diagnose slow workflows and data flow problems across different infrastructure configurations.

What is the best way to troubleshoot n8n expression errors?▼

The best way to troubleshoot n8n expression errors is enabling detailed logs and using Set nodes to inspect intermediate data, allowing you to isolate syntax issues and apply concrete fixes to your workflow logic.

n8n workflow not working: what are the limitations of manual debugging?▼

Manual debugging limitations in n8n include difficulty reproducing intermittent failures and tracing complex data flow issues. Enabling detailed logs and using minimal data tests help overcome these constraints to identify errors effectively.