> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/build/variables/capturing-user-input.md).
# Capturing User Input
### Adding Capture User Input Element
To capture information entered by the viewer, you can add the 'Capture Input' element from the 'Add Element' menu.
Capture Input Element
You can customize the Capture Input element in the Properties Panel - you can update the input's placeholder, min and max length to be entered by the viewer.
Capture Input setting panel
### Add Rules to activate it
You need to create rules to collect the data entered by the viewer.
Rules - Boolean Variables
### Viewer Screen
Here is how it looks to the viewer:
Capture Input front end
### Example Experience
{% embed url="" %}
Capturing User Input
{% endembed %}
These are the rules used in the above experience:
Rules - Capture Input into String Variable
a
---
# 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://docs.gmetri.com/metaverse/build/variables/capturing-user-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.
