# User Input

## User Input Node

This node gives you the ability to enter responses by typing or selecting responses from options provided in the listing. Without this Input, the flow will not proceed further during execution. This is similar to annotating or training your model. Since almost all conversational bots give an introductory message and wait for the user to enter a request, you can see why the first node in a workflow is often the **User Input** node.\
\
**To start with the User Input Node:**

1. Start to build the flow by dragging the first **User Input** node from the node palette on the left and drop it onto the center of the canvas.\
   \
   **NOTE:** You can set the Node to **Read Only** if it will contain pre-filled or informational data only.

<div align="left"><figure><img src="/files/R8LRPByvamQG0NeeXkDW" alt="" width="375"><figcaption></figcaption></figure></div>

2. Edit the user input and click on “OK”.

### **Single-Step Input**

In the example below, we select an option list and provide a value and label by“ticket id” respectively. Also, provide an output variable.

![](/files/gmuKcWnbf4MQB5E4kxJt)<br>

Shows options list to the user in the form of buttons (as seen in display type) and they canselect what they need.

### Multi-step input&#x20;

The next example is about ordering a phone. The user input asks which iphone andspecification.

Drag the user input node from the node palette. Then select option lists as inputtype and provide different models of Iphones, then click on OK. Three different models are used to showcase as an example here.

Next, add another user input node from the node palette is used to ask for thecapacity of the phone. This same method will pertain to any query required. The following screenshot shows how the workflow develops to respond to the user input as it narrows down what the user wants.

<div align="left"><figure><img src="/files/LdOtsf3l5qUJrXWzOwxf" alt="" width="563"><figcaption></figcaption></figure></div>

### Using an Output Variable&#x20;

&#x20;Add a new user input node under each leaf decision branch, with a message providing a reopen option. In addition, get the order decision (Yes or No) and use it as the user input value.

This gives users the option to confirm their choice with Yes/No buttons.

<div align="left"><figure><img src="/files/2uZtTotAgHe3H8fw8x37" alt="" width="563"><figcaption></figcaption></figure></div>

The user's choice will confirm whether to reopen the Ticket. If the user chooses ‘Yes’, it will reopen the Ticket, and if they choose ‘No’, then the ticket will remain closed.

### **Read-Only Option for User Input Node**

The **User Input** node gives users the ability to enter responses by typing or selecting responses from options provided. Without this Input, the flow will not proceed further during execution.

<div align="left"><figure><img src="/files/vVy8Ke0uhJ2WZWcIcQ7v" alt="" width="395"><figcaption></figcaption></figure></div>

Now you can set the **Input Node** to **Read Only** if it contains pre-filled or informational data only.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/workflow-reference-guides/workflow-nodes/user-interaction-conversational/user-input.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.