> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/web/textbox/send-keystrokes-values.md).

# Send Keystrokes Values

This action in Avo Assure is available under the **Captured Textbox Element**. The functionality of this Action in Avo Assure is to send individual keystrokes to the textbox, allowing each keystroke value to be entered one by one. The result of this action is stored in a dynamic variable for further use during test execution.

## **Syntax**

**Input Value**: `<input value>`

| Argument                            | Description                                                   |
| ----------------------------------- | ------------------------------------------------------------- |
| <p>\<input value><br>(Required)</p> | Specifies the actual string to be entered as the input value. |

**Output Value**: `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

| Argument                                                    | Description                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | both dynamic variable stores the status as **True** or **False**. |

### Example: Sending Individual Keystrokes to a Textbox

In this example, we explain how to send individual keystrokes to a textbox using the **Send Keystroke Values** action.

* **Action**: Send Keystroke Values
* **Input Value**: Van <Goodman@gmail.com>
  * The input value (**Van <Goodman@gmail.com>**) specifies the text to be entered into the target textbox.
* **Output Value**: {Status}
  * The result of the text entry operation is stored in the **{Status}** dynamic variable, which returns one of the following values:
    * **True**: If the keystrokes are sent to the textbox successfully.
    * **False**: If the keystrokes are not sent to the textbox successfully.
* **Logical Explanation**: The **Send Keystroke Values** action takes the value from the **Input Value** column (**Van <Goodman@gmail.com>**) and automates keyboard interactions by sending each character sequentially to the specified textbox. The result of this operation is stored in the **{Status}** variable as true.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Frw6QOKRBFtdI5xCpaW51%2Fimage.png?alt=media&amp;token=1ee5b119-6ec0-429b-bb83-d6d65f08cedd" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/web/textbox/send-keystrokes-values.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
