Input
Uncontrolled node
Overview
The Input node reads data from workflow inputs by name. Use this node to access values passed into the workflow from external sources, such as API calls, form submissions, or parent workflows. The node automatically retrieves the specified input value and makes it available as a data output for downstream nodes.
Inputs
This node has no input sockets. Instead, it reads from the workflow's input scope based on the configured Name property.
Outputs
| Output | Type | Description |
|---|---|---|
| value | Data | Contains the value of the workflow input specified by the Name property. Returns undefined if the input does not exist. |
Properties
| Property | Type | Description | Default |
|---|---|---|---|
| Name | Text | The name of the workflow input to read. This should match the key of the input data passed to the workflow. | - |
Runtime Behavior
The Input node is uncontrolled, meaning it runs automatically when the workflow starts without requiring an event trigger. During initialization, the node connects to the workflow's global input scope using the value specified in the Name property.
At runtime, the node first checks if an input with the specified name exists in the current execution context. If found, it outputs that value. If not found in the immediate inputs, it attempts to retrieve the value from the parent workflow's data scope (for sub-workflows).
Example
Reading an API Input
If your workflow is triggered by an API call with a JSON payload like:
{
"customerId": "12345",
"email": "user@example.com"
}
Configure the Input node with:
- Name:
customerId
The node will output "12345" through its value output, which can then be connected to database nodes, AI prompts, or other processing nodes.
Using with Sub-workflows
When used inside a Sub-workflow (Workflow node), the Input node can read inputs passed from the parent workflow. If the parent passes data named userData, setting the Input node's Name to userData will retrieve that value for use within the sub-workflow.