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

# Variables explorer

The Explorer's Variables tab: the App's named values, their defaults, secrets and live values, and how you reference them.

A variable is a named value of the App, written `$name`. The Variables explorer lists them all, with what each one holds right now.

Open it with the **Variables** icon in the Explorer's icon rail. What a variable is for, and when to use one instead of a wire, is in [Variables and endpoints](https://docs.heisenware.com/concepts/variables-and-endpoints.md).

<figure><img src="https://3495989837-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5Ketpww1s7TauSAJrJ8%2Fuploads%2Fgit-blob-a61d709375cb7987850b32793dab5c435692cd02%2Fbuilder-variables-explorer.png?alt=media" alt="The Variables explorer: a constant with its value, a variable the flow writes, a secret with its lock, and the three built-ins below them" width="262"><figcaption></figcaption></figure>

## The list

The panel shows how many variables the App has, then the variables themselves and, at the foot, the built-ins:

* A pencil icon and *constant value* mark a variable nobody writes. These come first.
* A bolt icon marks a variable an output or an extension writes, and the line below the name says which function feeds it.
* A lock marks a secret.
* Under **Built-in** stand `$USER`, `$LOCALE` and `$TIMEZONE`. The platform computes them, they are the same in every App, and you cannot change them.

Every row shows the variable's live value on the right, as it is at this moment. A secret never shows one: its value is not read back, not even here.

Hover a row and the Flowboard lights up every item that writes or reads this variable. Hover the name alone to see its description.

## Creating one

Click **+** (New variable) at the top of the panel:

* **Name**: camelCase, unique in the App. The `$` is not part of the name.
* **Description**: what the value is for. Other members and the assistant read it.
* **Secret**: the value is encrypted and masked everywhere. Use it for every credential. A variable that is secret stays secret.
* **Default value**: read like YAML. `42` is a number, `'42'` is text, `[a, b]` is a list, anything else is plain text. The type matters: a database column of text does not match the number `42`.

Click **Create**. The variable exists from that moment, with its default as its value.

The faster way for a value your logic produces: right-click the output, the modifier, the filter or the error handler that produces it and choose **Make variable…**. The dialog asks for a name and a description only, and the item becomes the variable's producer.

## Using a variable

* **In an input**: `$machine` as the whole value, or `${machine}` inside a text, as in `Line 2: ${machine} stopped`. Right-click the input and use **Insert Variable** to pick one from the list, which writes the braced spelling, safe in either place. Dragging the row onto an input writes `$machine`.
* **In an expression**: `$machine` is a value you compute with, not text that is pasted in. The editor of a [modifier](https://docs.heisenware.com/app-builder/app-builder/flowboard/modifier.md) or a [filter](https://docs.heisenware.com/app-builder/app-builder/flowboard/filter.md) has a **$** button that inserts one.
* **In an address**: type `$machines` into the agent or instance box of a dynamic address. See [Addresses](https://docs.heisenware.com/concepts/executors-and-instances.md#addresses-where-a-call-goes).
* **To feed it**: drag the row onto an output or an extension. That item then publishes its value into the variable, the same as **Make variable…** does.

A variable never runs anything. An executor reacts to a new value only through a hot input that reads it. See [Triggers and wires](https://docs.heisenware.com/concepts/triggers-and-wires.md).

## Renaming and removing

Both start on the row, with **Edit** and **Delete**.

A rename moves everything that was wired to the variable, because that wiring points at the variable itself, not at its name. Text does not move: a `$name` you typed into an input or an expression keeps its old text and stops resolving. The dialog lists every such place before it renames, and you can go back.

A delete does the same in reverse: the items that fed the variable are unassigned, and the typed references stay as they are and resolve to nothing. The dialog lists both before you confirm with **Remove**.

{% hint style="info" %}
A secret is not part of an exported [bundle](https://docs.heisenware.com/app-builder/app-builder/test-and-deploy.md). After an import you enter it again.
{% endhint %}


---

# 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.heisenware.com/app-builder/app-builder/variables.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.
