> 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/desktop/tree/get-node-name-by-index.md).

# Get node name by index

This is a pre-built action available under the **Captured Tree Element** from the **Desktop Application**. The functionality of this action in Avo Assure is to fetch the node's name based on the index provided in the input, and save the result in dynamic variable.

### Syntax

**Input Value:** `<Path (Separated by ;)>`

| Argument                                         | Description                                                                                                                                                    |
| ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<Path (Separated by ;)></p><p>(Required)</p> | <p>Specify the index whare the node is available in tree element</p><p><strong>Note: Each value can separated by semicolon</strong> <strong>( ; )</strong></p> |

**Output Value:**

<table><thead><tr><th valign="top">Argument</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><p>&#x3C;Dynamic Variable></p><p>(Required)</p></td><td valign="top">This dynamic variable holds the retrieved node name.</td></tr><tr><td valign="top"><p>&#x3C;Dynamic Variable></p><p>(Optional)</p></td><td valign="top">This dynamic variable holds the status of the action as <strong>True</strong> or <strong>False</strong>.</td></tr></tbody></table>

**Example:**

**Retrieves a node’s name from a tree element based on the specified index**

The **Get node name by index** action takes the value from the Input Value column (e.g., **1;2;3;4**) and fetches the node name located at the index position within the captured tree element. The fetched node name is stored in the **{Node Name}** variable (e.g., **Cursors** )

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FeE8FgLtmMoet2v4cgx1N%2Fimage.png?alt=media&amp;token=0c67d635-bde7-4544-8119-2c44857bab5c" 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/desktop/tree/get-node-name-by-index.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.