Ask for Input

Overview#

Ask one question or collect several related answers when the workflow starts.

Use this block when its responsibility is clear in the graph. Give it a name that describes the work it performs, then test it with representative input before publishing.

Working examples#

These are complete starting points, not decorative diagrams. Every graph is also available in the main template library and is checked by the workflow compiler.

1. Customer support intake#

You will build: A complete ticket with urgency and next action.

Collect the facts support needs before any model runs. Required fields prevent empty tickets from entering the workflow.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

2. Creative campaign brief#

You will build: A usable creative direction from one structured brief.

Long-form input keeps goals and constraints together. The runner can review the full brief before spending model credits.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

3. Public page reviewer#

You will build: A review plan tied to one validated URL.

A URL field makes the expected input obvious. Input validation catches malformed links before downstream work starts.

Open this template and adapt the labels, prompts, or credentials to your own workflow.

File uploads#

Set a question's answer type to File upload when the runner provides a document, image, or code file. Runners can choose a file, drag it in, or paste it:

• Keyboard: press ⌘V or Ctrl+V anywhere on the run form. The file goes to the upload field that has focus. With nothing focused, it goes to the only field with room, one file per field when several are empty, or the runner picks the field.
• Paste button: every upload field has a Paste button for phones and tablets. If the browser blocks clipboard access, the field shows a paste area to touch and hold instead.
• Pasted text: pasting text into an upload field offers to attach it as a file. The runner can rename it, for example to main.py, so the model knows the format.

Turn on Allow multiple files to accept several files for one question, up to 10 (choose a lower limit if you like). Files in one question can total at most 50 MB. Every file reaches the next block together, so one Generate Text block can compare or summarize all of them.

Through the API, send a multiple-file answer as a list of file objects. A single file object is accepted too and treated as a list of one.

Ports#

• Output: Data (out-right): any, optional, single.

Inspector#

• Question group title: key title; text; default: "Questions"; Example: e.g. Project brief.
• ask-for-input editor: manages fields with edit, validate, preview support.

Behavior#

• Input requirement: This is an entry node and does not accept an inbound connection.
• Execution: Handled by the handler using input.
• Timeout: No node-level timeout is defined.

Cost#

No metered provider or compute cost is assigned to this node.

Security#

• No credentials are used.
• The node has no external side effects.

Retry#

The runtime may retry this node according to the compiled execution policy.

Production checklist#

• Test the happy path and one malformed or empty input.
• Keep credentials out of prompts and published graph configuration.
• Set a timeout and retry policy that matches the operation's side effects.
• Name the final result so a runner can tell what success looks like.