> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.11.0/helmut4-components/helmutfx/preferences/helmut-variables.md).

# Helmut Variables

Helmut variables can be used within the streams or preferences to dynamically replace a key with a value. Alternatives to this variables are [Store Variables](/helmut4-releases/v4.11.0/helmut4-components/streamdesigner/stream-variable-store.md) or [Temporary Variables](/helmut4-releases/v4.11.0/helmut4-components/streamdesigner/nodes/actions/misc/stream-set-temporary-variable-action.md).

Those variables can be used for dynamic cascades and reduce the amount of static paths.\
\
**Example**

Path of AME Application in AME Render Node: /Applications/Adobe Media Encoder 2023/Adobe Media Encoder 2023.app\
\
By using a helmut variable this can be changed to the following

<figure><img src="/files/hNsEqKvLgHFufxGhKhCu" alt=""><figcaption><p>Helmut variable in preferences</p></figcaption></figure>

After setting up this variable the new path would be: {helmut.variable.AME Path}

Please have a look into [Helmut Variable ?](/helmut4-releases/v4.11.0/helmut4-components/streamdesigner/wildcards/variable-related-wildcards-3/helmut-variable.md) for a detailed information how to use the dedicated wildcard.

{% hint style="warning" %}
Helmut variables ***ARE case sensitive*** - please pay attention for correct usage\
"AME Path" & "AME path" would give you two different results
{% 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 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.helmut.de/helmut4-releases/v4.11.0/helmut4-components/helmutfx/preferences/helmut-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.