> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/get-element-by-name.md).

# Get Element by Name

{% hint style="info" %}
**Block Information**

Available in: Page Flow

Toolbox Category: Html/DOM

Block Type: [Output](/app-editor/page-flow/block-anatomy.md#output-block)

Output Type: [*element*](/app-editor/page-flow/references/value-types.md)
{% endhint %}

**`Get Element by Name`** is an [output block](/app-editor/page-flow/block-anatomy.md#output-block) that allows you to retrieve a reference to any element on a page or form by providing it's [name](/app-editor/page-editor/page-element-settings.md#name) . The output is of type [*element*](/app-editor/page-flow/references/value-types.md) and is compatible with [Value Parameters](/app-editor/page-flow/block-anatomy.md#value-parameters) of type [*element*](/app-editor/page-flow/references/value-types.md) or of type [*any*](/app-editor/page-flow/references/value-types.md).

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FsX3fvcXdG1RnYA4cwgWC%2Fimage.png?alt=media&amp;token=24263f4c-dad6-485b-8457-6a8766af82af" alt="" width="260"><figcaption><p>Get Element by Name block</p></figcaption></figure></div>

The block consists of *Name* a [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a *text* value representing the [name](/app-editor/page-editor/page-element-settings.md#name) of the element.

{% hint style="warning" %}
NOTE: If there are multiple elements with the same name, this block outputs a reference to the first such element.
{% endhint %}

***

## Usage Example

The image below shows an example of the Get Element by Name block where the value of the [Input](/app-editor/page-editor/built-in-elements/input.md) element named "*Input28*" is set to the text "*Hello!*" using the [Set Input Value](/app-editor/page-flow/toolbox-blocks/set-input-value.md) block.

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2F41f7JfkyVo5RwIeUD2ck%2Fimage.png?alt=media&amp;token=29f36c0d-43a0-456a-9038-f1f80e117518" alt="" width="563"><figcaption><p>Example of Get Element by Name</p></figcaption></figure></div>


---

# 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.zingy.ai/app-editor/page-flow/toolbox-blocks/get-element-by-name.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.