Input
Input blocks sit in the builder palette under Basic → Input. They belong on chat workflows. Each one pauses until the person in the session answers. They are invalid on a general graph (no user to wait on). Shared graph rules are on Workflows.
The answer is written to the data pipe. Optionally store it under Binding Variable → Key so later blocks can bind that name.
When the pipe is an object (location, upload, a calendar range, or each multi-select item), a table write matches column keys to those property names. Keys are case-sensitive: use lat and lng, not Lat and Lng. Display labels on the column do not matter.
Shared inspector sections on every input type:
| Setting | Description |
|---|---|
| Prompt | Message shown before the control (optional on most types) |
| Binding Variable → Key | Optional context name for the answer |
| Navigation → Back / Skip | Let the person go back or skip this step |
| Error Handler | Throw (fail the run), Retry (ask again with Retry Prompt), or Ignore (continue without a value) |
| Use | Block |
|---|---|
| Typed text (email, number, and similar) | Text |
| A file | Upload |
| A map location | Location |
| Stars / score | Rating |
| Date or time picker | Calendar |
| Several checkboxes | Multi Select |
To show something without waiting, use Output. List and carousel also wait for a selection.
6