n8n-debugging-official

n8n Debugging When something breaks, the cause is almost always: Parameter misconfiguration (wrong value, wrong type, missing field). Stale assumptions (different version, different behavior than you remember). Paths misconfigured or misconnected (wrong output index, wrong merge input, missing wire, IF/Switch wired to the wrong branch). Upstream data stripped (an intermediate node replaced $json with its own output, so downstream $json.x resolves to null even though "it should be there"). Fix: reference the stable upstream node by name ( $('Earlier Node').item.json.x ). Item context lost (after Aggregate, Execute Once, or Split Out flows, n8n can't pair .item references deterministically, error reads like "The expression is referencing... multiple matching items"). Fix: Merge node to re-establish context, $input.all().find(...) for explicit lookup, or redesign to keep item correspondence stable (e.g., split into stateless sub-workflows). Logical errors (the wires are right and the parameters are right, but the workflow does the wrong thing, same as a logic bug in code). Genuine bug (rare but real). Diagnose systematically: cheap checks first, deeper investigation only when those fail. Non-negotiable Believe the user. "This isn't working" means something isn't behaving as they expect, even if they describe the symptom imprecisely. Don't dismiss with "it should work" or "are you sure you're doing X?". Investigate first: the user is truth about what should happen, execution data and source are truth about what is happening. When you can't find the cause, "I don't know yet" beats a plausible-sounding fabrication. Strong defaults (cause to cheap check) Show more Installs 906 Repository n8n-io/skills GitHub Stars 444 First Seen Jul 7, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Warn