Builder questions

What they are

Builder questions are the questions an end user answers before running an agent. The builder defines them during the publish flow, and the answers are injected into the user's private copy of the workflow at run time. They are stored with the agent as its consumer-input schema, so the run page, the chat surface, and the test step all render the same questions.

How to select them

In the publish flow, the "All nodes" step lists every node of the workflow with its input fields. Each field has an "Ask user" switch:

• Switch on the fields whose value should come from the end user on every run: the topic of a post, a recipient, a dish name, a preference.
• Leave the switch off for configuration that stays fixed: prompts the builder tuned, API paths, formatting choices. Those keep the value wired in the workflow.

Form-trigger fields are selected by default. Fields on action steps can also be exposed, including dropdowns whose options resolve live against the end user's own connection (for example a Slack channel list), date, checkbox, number, and list inputs. File-upload fields are not supported. Fields that carry secrets can be marked as secret so the value is masked and stored safely.

How to write the questions

After selection, the "Input fields" step shows each chosen field and a box: "Question shown to the user". Guidelines:

• Write in plain user language, not field names. "Which role is this post about?" rather than role.
• One question per field, and state the expected format when it matters: “Any dietary preference? (vegetarian, vegan, gluten-free)”.
• Use the optional description as helper text under the question, never as a second question.
• For choice fields, add options so the user picks instead of typing.