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
| Name | Type | Required | Description |
|---|---|---|---|
input | any | No | Pipeline input data (overrides defaults) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
output | any | No | Validated and merged input data passed to downstream nodes |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Default Values | defaults | json | No | Default key-value pairs applied when inputs are missing | ||
| Data | data | json | No | Additional default data (synonym for defaults, commonly used in pipeline YAML) | ||
| Required Fields | required_fields | array | No | List of field names that must be present in the input |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Type Schema | schema | json | No | Map of field names to expected types (string, number, boolean, object, array) for validation | ||
| Transforms | transforms | json | No | Map of field names to transform operations (to_string, to_json) |