Add optional request validation to the Webhook node

It would help if there was a node for:

An optional request-validation feature in the existing Webhook node, using JSON Schema or configurable visual fields.

Our use case:

We use n8n Webhook nodes to expose REST-style API endpoints. Incoming requests often need validation for required fields, types, nested objects, arrays, allowed values, formats, and additional properties.

Currently, users must build this validation manually with expressions, Set, If, or Code nodes. This makes API workflows repetitive and makes consistent HTTP 400 validation responses difficult.

We built a prototype community node to explore this use case:

The prototype is a generic REST/Webhook node, so it does not fit the current verified-node model because it overlaps with the built-in Webhook node and does not integrate one specific third-party service. We believe this capability may be better implemented as an enhancement to the existing Webhook node.

Possible approaches include:

  1. Add validation directly to the Webhook node.
  2. Create a reusable request-validation component for trigger nodes.
  3. Create a dedicated REST API node that reuses Webhook behavior.

The first option seems the most suitable because it avoids duplicating the existing Webhook node.

Any resources to support this?

Are you willing to work on this?

Yes. We are willing to help with the design, implementation, tests, and documentation based on the direction recommended by the n8n team.