> 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/custom/send-keystroke-values.md).

# Send Keystroke Values

This is a pre-built action in Avo Assure and is available for the **@Custom Element.** The functionality of this action in Avo Assure to send the string values individually on the object specified in the input and saves the result in the given dynamic variable.

### Syntax

**Input Value:**`<ObjectType>;<VisibleText(optional)>;<Index>;<value>;<abs(optional)>`

| Argument                            | Description                                                                                                               |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| <p>\<ObjectType><br>(Requred)</p>   | Provide the object type to which the value will be typed (e.g., textbox)                                                  |
| <p>\<VisibleText><br>(Optional)</p> | Enter the visible text on the object                                                                                      |
| <p>\<Index><br>(Required)</p>       | Provide the position of the element, which helps to identify the value based on the sequence in list . (starting from 0)​ |
| <p>\<value><br>(Required)</p>       | Specify the string to be typed (e.g., John, abc123)                                                                       |
| <p>\<abs><br>(Optional)</p>         | If the **abs** is provided, the action is performed with absolute identification using the **absolute X path**            |

{% hint style="warning" %}
**Note:** *The user needs to provide the type of object, its visible text of the element (if needed), its element index, and the abs.*

*To skip an optional input value, use an extra semicolon (;).*
{% endhint %}

#### Output Value

| Argument                                                    | Description                                                     |
| ----------------------------------------------------------- | --------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This dynamic variable holds the result as **True** or **False** |

**Example**

**Sends string keystrokes to a specific object on the application**

The **send Keystroke Values** action takes the value from the Input Value column (e.g., **textbox;;1;Pass\@1999**) and types the string value into the specified object character by character. The result of the keystroke entry is stored in the **{Keystroke}** variable, with the following possible values:

* **True** – if the string is successfully typed.
* **False** – if the action fails

<figure><img src="/files/JK80ufGAKCEKYiDxpgNJ" 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 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.avoautomation.com/avo-assure/actions/web/custom/send-keystroke-values.md?ask=<question>&goal=<endgoal>
```

`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.
