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
Output ports
Settings
Basic
Advanced
Errors
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.