Workflow Input

Ask the customer one clear question and turn their answer into data your workflow can use.

Overview#

Workflow Input is where customer data enters your product. It shows a question in the run modal and passes the answer downstream as structured data.

Use it whenever your workflow starts with something the customer must provide: a prompt, a URL, a file, or a choice from a list.

Workflow Preview

Read-only builder graph

Output , Data: The customer's answer, ready for the next block. No inputs; this block starts the flow.

Question: What you ask the customer. Keep it direct and outcome-focused.
Input Type: How the answer is collected , text, long paragraph, number, URL, dropdown, file upload (up to 5MB), or JSON.
Description: Optional help text shown under the question , examples, limits, or format hints.
Dropdown options: When Input Type is Dropdown, define the choices the customer sees.

Ask for only what the workflow actually needs.
Match the input type to the answer shape , do not use JSON when a short text field is clearer.
Use the description for examples or constraints, not to repeat the question.
Place this block at the start of any branch that depends on customer input.

Collect several run-modal fields in one grouped form, each with a stable key for downstream steps.

Define what the customer receives when the workflow finishes.

Combine several upstream values into one payload for the next step.

Ask the customer one clear question and turn their answer into data your workflow can use.

Workflow Input is where customer data enters your product. It shows a question in the run modal and passes the answer downstream as structured data.

Use it whenever your workflow starts with something the customer must provide: a prompt, a URL, a file, or a choice from a list.

Workflow Preview

Read-only builder graph

Output , Data: The customer's answer, ready for the next block. No inputs; this block starts the flow.

Question: What you ask the customer. Keep it direct and outcome-focused.
Input Type: How the answer is collected , text, long paragraph, number, URL, dropdown, file upload (up to 5MB), or JSON.
Description: Optional help text shown under the question , examples, limits, or format hints.
Dropdown options: When Input Type is Dropdown, define the choices the customer sees.

Ask for only what the workflow actually needs.
Match the input type to the answer shape , do not use JSON when a short text field is clearer.
Use the description for examples or constraints, not to repeat the question.
Place this block at the start of any branch that depends on customer input.