n8n-validation-expert

Run validate_node with the runtime profile, read each error message, fix errors one at a time, and re-validate. Most configurations pass within 2-3 iterations, which is the normal expected pattern.

A missing_required error means a mandatory field like channel, url, or query was not provided in the node configuration. Use get_node to list required fields, then add the missing property with a valid value.

Use the runtime profile for most pre-deployment validation since it balances coverage and noise. Use ai-friendly to reduce false positives by about 60 percent, minimal for quick checks, and strict only for critical production workflows.

No. Roughly 40 percent of warnings are acceptable depending on context, such as missing error handling in test workflows or unbounded queries on small known datasets. Always fix security warnings and document why accepted warnings were ignored.

Yes. Auto-sanitization runs on every workflow save and automatically fixes binary and unary operator structure issues, such as removing singleValue from equals operations or adding it to isEmpty. Do not manually fix these.

Invalid expression errors usually come from missing {{}} wrappers, typos in node names, or accessing webhook data without the .body prefix. Wrap expressions as ={{$json.body.field}} and verify referenced node names exist in the workflow.