Zum Hauptinhalt springen

Input

Category: Transform
Node id: input

Entry point for pipelines that accepts, validates, and transforms initial inputs with default values and type checking

What it does​

  • Default value injection for missing input fields
  • Required field validation with early failure
  • Type checking against expected schema (string, number, boolean, etc.)
  • Input transforms: to_string, to_json conversions
  • Merge of defaults with provided inputs

Use cases​

  • Define pipeline entry points with validated inputs
  • Provide default configuration values for parameterized pipelines
  • Enforce input contracts before downstream processing begins

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
inputanyNoPipeline input data (overrides defaults)

Output ports​

NameTypeRequiredDescription
outputanyNoValidated and merged input data passed to downstream nodes

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Default ValuesdefaultsjsonNoDefault key-value pairs applied when inputs are missing
DatadatajsonNoAdditional default data (synonym for defaults, commonly used in pipeline YAML)
Required Fieldsrequired_fieldsarrayNoList of field names that must be present in the input

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Type SchemaschemajsonNoMap of field names to expected types (string, number, boolean, object, array) for validation
TransformstransformsjsonNoMap of field names to transform operations (to_string, to_json)

Errors​

CodeDescription
MISSING_REQUIRED_FIELDA required input field is not present
TYPE_MISMATCHAn input field does not match the expected type in the schema

Runtime notes​

  • Output is a flat map of all merged keys — defaults first, then data, then actual inputs override both
  • The output port also contains an 'output' key with a copy of the full merged map for explicit port wiring
  • required_fields validation runs after merge — defaults can satisfy required fields
  • transforms (to_string, to_json) are applied last, after merge and validation

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..