> For the complete documentation index, see [llms.txt](https://docs.graphlinq.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graphlinq.io/dev-tooling/blocks/array/get-array-element-at-index.md).

# Get Array Element At Index

The "Get Array Element At Index" block in the GraphLinq IDE allows for retrieving a specific element from an array based on its index.

Block Description This block belongs to the Array category and is used for accessing individual elements in an array.

### Input Parameters

* Array (List): The array from which an element will be retrieved.

  Output Parameters
* Element (object): The retrieved element from the array.

### Example Use Case

In a graph processing sensor data stored in an array, the "Get Array Element At Index" block can be used to access specific data points at known intervals for analysis or alerting.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.graphlinq.io/dev-tooling/blocks/array/get-array-element-at-index.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.