> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/4-tresci/tresc-textcontent/wykorzystanie-zmiennych-w-tresciach.md).

# Using variables in Content

Artifact **Content (Text Content)** provides for the use of variables. To use variables, in **Content** we enter the variable name enclosed in `${}` , e.g. `${nowaZmienna}`

The variable name should match the value of the component id, or the mid of the session variable defined in the application template, which we refer to in **Content**.

An example using in Content the value from the session variable (with mid *zmienna1*) and the value of the text field (*GesTextField1*):

![Figure 1. Example of Content with a reference to the value of a session variable and a text field](/files/61ebe60516aade6baa3cf1f96c6a79ea9cfa370e)

{% hint style="info" %}
Demo application: demoTextContent
{% 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/biblioteka-komponentow-bazowych/4-tresci/tresc-textcontent/wykorzystanie-zmiennych-w-tresciach.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.