n8n-validation-expert

Fix n8n workflow validation errors by interpreting error types like missing_required or type_mismatch, applying structured recovery patterns, and running iterative validation loops until the config passes.

A type_mismatch or invalid_reference error in n8n indicates that an expression or node connection uses incorrect data types or points to a non-existent field. Apply auto-sanitization and structured validation loops to resolve these issues.

Handle false positives and warnings during n8n workflow debugging by evaluating them against documented recovery patterns, deciding when to accept them, and documenting the validation decisions to maintain workflow integrity.

Yes, you can use validation profiles to automate error triage for n8n configs. Profiles apply structured validation loops to categorize errors, warnings, and false positives while leveraging auto-sanitization to guide fixes.

The best way to debug an n8n workflow with invalid_expression errors is to run a validation cycle, review the error catalog references, apply the suggested fixes to the expressions, and re-validate until the config is valid.

If n8n workflow validation is not working, limitations may stem from unchecked false positives or undocumented warnings. Consult FALSE_POSITIVES.md, document edge cases, and ensure auto-sanitization rules match your validation profile.