> 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/sap/textbox-operations/get-text.md). # Get Text This is a pre-built action available under the **Captured Textbox Element** from the **SAP GUI Application**. The functionality of this action in Avo Assure is to fetch the text present in the textbox and save result in the dynamic variable. ### **Syntax** **Input Value:** `N/A`

Argument	Description
N/A	Not Applicable

**Output Value:**

Argument	Description
<Dynamic Variable> (Required)	This variable holds the extracted text from the textbox element
<Dynamic Variable> (Optional)	This dynamic variable holds the status of the action as True or False.

Argument

Description

(Required)

This variable holds the extracted text from the textbox element

(Optional)

This dynamic variable holds the status of the action as True or False.

**Example** **Fetches the visible text from the User Name Textbox element** The **Get Text** action does not require any value from the Input Value column. It retrieves the visible text **(e.g., acap3)**from the captured **User Name** element. The result of the action is stored in the **{Text}** variable as (e.g., **acap3**)

--- # 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/sap/textbox-operations/get-text.md?ask=&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.