> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2022.2/toolbox/array/insert-array-element.md).

# Insert Array Element

## Overview

![The Insert Array Element Node.](/files/0748YQ5rluyjCHKIYALm)

The **Insert Array Element Node** adds an element, or elements, to an **Array**. These are inserted at a specified index and given a specified value.

For example, an **Array** is populated as follows: $$\[0,6,12]$$. If the *indices* $$1$$ and $$3$$ are given and the values $$3$$ and $$9$$ are defined, the elements at those *indices* are inserted and the user is left with a new **Array**: $$\[0,3,6,9,12]$$.

[**Scope**](/incari-studio/2022.2/toolbox/overview.md#scopes): **Project**, **Scene**, **Function**, **Prefab**.

## Attributes

![The Insert Array Element Node Attributes.](/files/xUq98itphXoCLMe6fgqm)

| Attribute       | Type          | Description                                                                                            |
| --------------- | ------------- | ------------------------------------------------------------------------------------------------------ |
| `Index [n]`     | **Drop-down** | Specifies each new element's `Index` in the **Array**, if one is not provided in the **Input Socket**. |
| `Data Type [n]` | **Drop-down** | Specifies each new element's `Data Type`, if one is not provided in the **Input Socket**.              |
| `Value [n]`     | **Drop-down** | Specifies each new element's `Value`, if one is not provided in the **Input Socket**.                  |

## Inputs

| Input             | Type      | Description                                                                                                 |
| ----------------- | --------- | ----------------------------------------------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse** | A standard **Input Pulse**, to trigger the execution of the **Node**.                                       |
| `Array`           | **Array** | The starting **Array** to have element(s) added.                                                            |
| `Index (i)[n]`    | **Int**   | The index `i` where the element will be inserted. `n` determines the number of **Input Sockets** available. |
| `Value`           | **Int**   | The value(s) of the element(s) to be added.                                                                 |

## Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |
| `Array`            | **Int**   | The resulting **Array** with the inserted element(s).                                                                                  |

## See Also

* [**Remove Array Element**](/incari-studio/2022.2/toolbox/array/remove-array-element.md)


---

# 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.incari.com/incari-studio/2022.2/toolbox/array/insert-array-element.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.