Aller au contenu principal

Validator

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​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
datajsonYesData object whose fields are validated against the rules

Output ports​

NameTypeRequiredDescription
resultjsonNoValidation result containing valid, errors (array of field/rule/message), and data (original input passthrough)
successbooleanNoWhether the operation succeeded (distinct from validation passing)

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Validation RulesrulesarrayYesArray of validation rules; each has field, type, and type-specific options

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Strict Modestrict_modebooleanNofalseWhen true, returns an error instead of passing through on validation failure

Errors​

CodeDescription
VALIDATION_FAILEDOne or more validation rules failed (strict mode)
INVALID_RULESRules configuration is missing or not a valid array
INVALID_PATTERNRegex pattern in a pattern validation rule failed to compile

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.

Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.