Inputs
Collect data from users at runtime with text fields, file uploads, date pickers, and more
Overview
Input nodes define the data your workflow needs from users at runtime. When someone runs your workflow, they see a form with the input fields you’ve configured — text boxes, file uploads, date pickers, dropdowns, and more.
Input nodes are different from Static nodes: inputs require user interaction each time the workflow runs, while static nodes provide fixed values that never change.
Basic
Standard input fields for collecting user data at runtime.
Date picker for selecting dates
File upload for documents, images, and other files
Multi-line text input for longer content
Dropdown menu with predefined options
Single-line text input for short values
URL input with validation
Integrations
Input fields that connect to external services for file selection.
Static
Fixed values embedded in the workflow that stay the same across all runs — no user input required.
Embed fixed images directly in the workflow
Embed a fixed text value in the workflow
Embed fixed videos directly in the workflow
Inputs vs Static nodes
| Feature | Input nodes | Static nodes |
|---|---|---|
| User interaction | Required at runtime | None |
| Value changes | Different each run | Fixed for all runs |
| Use case | Dynamic user data | Constants, templates, fixed assets |
| Examples | Short Text, File, Date | Static Text, Static Image |
Use Input nodes when the value should be provided by the user each time the workflow runs. Use Static nodes when the value is set once in the editor and stays constant.