You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If some JSON fails validation against a the given Schema, you should not throw a NodeApiError as this stops the execution. Do data is passed onto the next node.
It would be best if this could pass the error out on an Error branch and not throw a 400
A subsequent node connected to the error branch could interrogate the "instancePath", "keyword", "message" etc, and handle the error.
This would be great when used in conjunction with Webhook nodes to validate POST bodies and return meaningful error responses.
Hi
If some JSON fails validation against a the given Schema, you should not throw a NodeApiError as this stops the execution. Do data is passed onto the next node.
It would be best if this could pass the error out on an Error branch and not throw a 400
A subsequent node connected to the error branch could interrogate the "instancePath", "keyword", "message" etc, and handle the error.
This would be great when used in conjunction with Webhook nodes to validate POST bodies and return meaningful error responses.
See also https://community.n8n.io/t/using-n8n-nodes-data-validation/44093
thanks in advance
The text was updated successfully, but these errors were encountered: