n8n-debugging

Diagnose failing n8n workflow executions using execution data and node schemas.

421|46|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/n8n-io/skills --skill n8n-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-debugging
Source: https://github.com/n8n-io/skills/tree/main/skills/n8n-debugging
Command: npx skills add https://github.com/n8n-io/skills --skill n8n-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you figure out why an n8n workflow fails or produces incorrect results, turning vague “it’s not working” reports into a structured diagnosis.

Core Features & Use Cases

  • Systematic root-cause triage that prioritizes cheap checks first (parameter misconfiguration, stale assumptions, wiring/connection issues).
  • Execution- and workflow-grounded investigation using tools like get_execution and get_workflow_details to confirm the failed node, inputs, and actual runtime behavior.
  • n8n-specific debugging heuristics for common failure patterns such as upstream data stripped, lost item context after fan-out/aggregate steps, logical errors, and genuine bugs, with guidance to consult n8n source when needed.
  • Version drift handling by prompting for n8n instance version and skills plugin update timing when behavior diverges from expectations.
  • Practical escalation and workaround guidance via community and GitHub issue paths when the bug is confirmed.

Quick Start

Ask the skill to debug your issue by stating what you expected, what happened, the error message (if any), and when it last worked.

Frequently Asked Questions about n8n-debugging

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

FAQPage Schema
How do I debug a failing n8n workflow execution?

Debug failing n8n workflows by correlating execution data with workflow configuration and node schemas. Use MCP tools like get_execution and get_workflow_details to inspect the failed node, inputs, and runtime behavior to pinpoint root causes.

Why does my n8n workflow output missing fields after an aggregate step?

Missing fields in n8n outputs often stem from lost item context after fan-out or aggregate steps. Inspecting upstream data flow and validating data shapes against node type schemas helps identify where the context was dropped.

What is the best way to diagnose parameter misconfiguration in n8n nodes?

Diagnose n8n parameter misconfiguration by validating node parameters against their expected schemas. Checking the workflow configuration and upstream data flow confirms whether the node received the correct input shape before failing.

How do I handle version drift between my n8n instance and the skills plugin?

Handle n8n version drift by checking your instance version and skills plugin update timing. When behavior diverges from expectations, comparing versions helps determine if the issue is a genuine bug or a compatibility mismatch.

What should I do when an n8n workflow produces incorrect results without error messages?

For incorrect n8n workflow results without errors, inspect the execution data to trace unexpected outputs. Analyzing the upstream data flow and node connections reveals logical errors or miswired connections causing the silent failure.

Can I use this skill to debug n8n pagination and data-shape issues?

Yes, you can debug n8n pagination and data-shape issues by inspecting execution data and validating parameter inputs. The investigation applies n8n-specific debugging heuristics to confirm if the node received the correct data structure.