Input
Triggerarrow.right.circle
trigger.input
Manual trigger that provides user-defined input when run. Unlike other triggers that fire automatically based on events, the Input trigger requires you to manually start it, providing data each time.
Choose between text, JSON, or file input modes. This is ideal for testing workflows, building interactive tools, or creating workflows that process user-provided data on demand.
Ports
| Direction | Name | Data Type | Description |
|---|---|---|---|
| Outlet | Output | Any | Payload emitted when the workflow is manually run |
Configuration
| Field | Type | Default | Description |
|---|---|---|---|
| Input Type | Dropdown |
Text | Type of input: Text, JSON, or File |
| Text | Text Area |
— | Free-form text input Visible when Input Type is Text |
| JSON | JSON Editor |
— | Structured JSON input with validation Visible when Input Type is JSON |
| File | File Picker |
— | Path to a file to process Visible when Input Type is File |
| Custom Arguments | Key-Value |
— | Additional key-value pairs included in the output payload |
Output Variables
| Variable | Type | Description |
|---|---|---|
text |
String | Text representation of the input |
contentType |
String | Input type (text / json / file) |
data |
Any | Parsed input data (text string, JSON object, or file path) |
filePath |
String | File path (when input type is file) |
timestamp |
String | ISO 8601 timestamp of the run |
Example
Manually provide JSON data, format an auth header, and post to an API endpoint: