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

# Variables

Personalise your text blocks

Throughout the platform you sometimes have the ability to use variables in text blocks. Some examples are:

* [Documents](https://docs.eventication.com/event/general/documents.md)
* [Bulk email](https://docs.eventication.com/event/communication/bulk-email.md)
* [SMS](https://docs.eventication.com/event/communication/text-messages.md)
* Many other text fields

Variables are constructed of a key and some special characters.

```
{{email}}
```

This is an email variable with the characters `{{` and `}}`. When the text is rendered these variables will be replaced with the actual values of the person receiving the text or document. This means `{{email}}` will be replaced with the email address of this person.

Different text fields have different variables. Different kinds of users (members, list visitors) have different variables. Underneath every text field that supports variables you can find a button to show all the options.

<figure><img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fgit-blob-7f7340a6480602144cdf703a7863355d2be4d9ba%2FScreenshot%202023-10-06%20at%2011.00.12.jpg?alt=media" alt=""><figcaption><p>An example of the button where you can find all variables</p></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eventication.com/event/misc/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.
