> 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/get-text-from-object.md).

# Get Text From Object

This is a pre-built Action located under the captured textbox element. The functionality of this Action in Avo Assure is to retrieve the text from the textbox. The fetched text is stored in a dynamic variable for further use during test execution.

## Syntax

**Input Value**: `N/A`

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>N/A</td><td>Not Applicable</td><td></td></tr></tbody></table>

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

<table><thead><tr><th>Argument</th><th>Description</th><th data-hidden></th></tr></thead><tbody><tr><td>&#x3C;Dynamic Variable><br>(Required)</td><td>This dynamic variable stores the retrieved text from the object.</td><td></td></tr><tr><td><p>&#x3C;Dynamic Variable></p><p>(Optional)</p></td><td>This dynamic variable stores the status as <strong>True</strong> or <strong>False.</strong></td><td></td></tr></tbody></table>

### **Example: Get Text from a Specified Object**

In this example, we explain how to extract and store the visible text content from a specified object using the **Get Text From Object** action.

* **Action**: Get Text From Object
* **Input Value**: N/A
* This action does not require any input value in the **Input Value** column. It retrieves the visible text content from the targeted object.
* **Output Value**: {Text}
  * The retrieved text (e.g., Colby <Moses@gmail.com>) is stored in this **{Text}** dynamic variable.
  * If a second output variable is provided, the action returns the status as True/False:
    * **True**: If the text is retrieved successfully.
    * **False**: If text is not retrieved successfully.
* **Logical Explanation**: The **Get Text From Object** action identifies the specified object within the application and extracts the visible text displayed on it. The extracted text is stored in the **{Text}** variable (e.g., Colby <Moses@gmail.com>).

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FF6c610AuqSeQq80M8fgS%2Fimage.png?alt=media&amp;token=75b8af56-811b-4630-a1b4-ca3aaba5d7b0" 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/get-text-from-object.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.