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

# Get Link Text

This is a pre-built Action located under the **Custom** **element.** The functionality of this action in Avo Assure to fetch the link's text specified in the input value and saves the result in dynamic variable.

### **Syntax**

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

| Argument                            | Description                                                                                                    |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| <p>\<ObjectType><br>(Required)</p>  | Specify the type of object (e.g., hyperlink text)                                                              |
| <p>\<VisibleText><br>(Optional)</p> | Enter the visible text on the object (Optional)                                                                |
| <p>\<Index><br>(Required)</p>       | Provide the index of the object inside the page (starting from 0)                                              |
| <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:** *To skip an optional input value, use an extra semicolon (;).*
{% endhint %}

**Output Value**

| Argument                                    | Description                                                                          |
| ------------------------------------------- | ------------------------------------------------------------------------------------ |
| <p>\<Dynamic Variable><br>(Required)</p>    | This dynamic variable stores the retrieved link text                                 |
| <p>\<Dynamic Variable></p><p>(Optional)</p> | This dynamic variable stores the result of the verification as **True** or **False** |

**Example**

**Retrieves the visible text of a specified hyperlink element on the web page**

The **Get Link Text** action takes the value from the Input Value column (e.g., **link;;0**) and fetches the text content of the specified link. The result of the retrieval is stored in the **{Link}** variable, while the execution status is stored in the **{Status}** variable, with the following possible values:

* **True** – if the link text is retrieved successfully.
* **False** – if retrieval fails

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FoWKu7QxBgHnMnDPHENNM%2Fimage.png?alt=media&amp;token=92e0bc0c-4f4f-4bd7-bd19-293a68f4ea99" 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/custom/get-link-text.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.