Category: Control
Node id: validator
Validates input data against configurable rules (required, type, range, length, pattern, email, url, enum)
What it does
- Eight validation rule types: required, type, range, length, pattern, email, url, enum
- Regex pattern matching for custom validation
- Strict mode that halts pipeline on validation failure
- Detailed error reporting with field, rule, and message
- Data passthrough for valid inputs
Use cases
- Validate incoming FHIR resource fields before processing
- Enforce data quality rules on clinical data imports
- Gate pipeline execution on required field presence
Runtime
Output ports
Settings
Basic
Advanced
Errors
Runtime notes
- The result output is a VALIDATION REPORT, not the validated data itself. Original input data is nested inside result.data.
- To access original fields downstream, use a transform node with extract mode on paths like result.data.field_name.
- In strict_mode, the node returns an error and halts the pipeline instead of passing through.
- The data key inside result contains ALL inputs the validator received, not just the validated fields.
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.