n8n-validation-expert

Run validate_node_operation with the runtime profile, read each error message for the failing property and fix guidance, correct one error at a time, then re-validate. Expect 2-3 iterations before the configuration passes.

A missing_required error means a mandatory field was not provided in the node configuration. Use get_node_essentials for the node type to list required properties, then add the missing field with a valid value.

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

No. Roughly 40% 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 fixes binary/unary operator structure issues, such as removing singleValue from equals operations or adding it to isEmpty. Do not manually fix these; trust the automatic fix.

Invalid_reference errors occur when an expression or connection points to a node that was renamed, deleted, or never existed. Correct the node name in the expression or run the cleanStaleConnections operation via n8n_update_partial_workflow.