> For the complete documentation index, see [llms.txt](https://documentation.nomos-system.com/nomos-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.nomos-system.com/nomos-system/integrator-en/variables.md).

# Variables

In this view, you can create, manage, and use variables for automation purposes. A variable is a custom unit that can be used in automations to store states or values.

**Variable Overview:**

1. **Name:** Displays the name of the variable.
2. **Last updated:** Shows the date when the variable was last edited.
3. **Actions:**
   * **Edit (Pencil Icon):** Allows you to edit the selected variable.
   * **Delete (Trash Can Icon):** Deletes the variable.

Additionally, new variables can be added using the "Create" button at the top right.

<figure><img src="/files/8Amy5I6S5j4gwQ2yiSDo" 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 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://documentation.nomos-system.com/nomos-system/integrator-en/variables.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.