> For the complete documentation index, see [llms.txt](https://help.wotnot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.wotnot.io/build/action-blocks/collect-input.md).
# Collect input
Collect Input action block is used for asking questions to which your visitors can respond in the chat.
### Using the Collect Input block
Add the Collect Input block onto the canvas and connect it to the step before it. Click on the block to configure where the user’s response should be saved.
#### Configuration
* **Question**: The question you want the bot to ask when collecting the user's response.
* **Save response**: Select or create a variable where the user’s complete message will be stored. This variable can be referenced later in your workflow. [Learn more about variables](/build/interface/variables.md)
* **Add an info message**: Displays an info icon with helper text to provide additional context about this message.
{% hint style="info" %}
The chat flow will not proceed until this question is answered by the user.
{% endhint %}
{% hint style="info" %}
If your variable requires a specific kind of input which the user wrongly submits, the user will show an error message and not be allowed to proceed.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://help.wotnot.io/build/action-blocks/collect-input.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.