# Environment variables

[Environment variables](https://app.datamin.io/env-variables) allow you to set variables in one place and reuse them in tasks of pipelines and metrics as **ENV\_variable\_name**.

<figure><img src="/files/3pvffqfs3ADkzQ7n8OrE" alt=""><figcaption></figcaption></figure>

For example, if you have a KPI threshold equal to **100**, you can set its variable as **key="KPI\_THRESHOLD"** and **value=100** here and reuse it everywhere else as **ENV\_KPI\_THRESHOLD**.

<div><figure><img src="/files/p3fmbqwJiD8i2zCMzBdK" alt=""><figcaption><p>Using environment variables in API Calls</p></figcaption></figure> <figure><img src="/files/gnvWamPkNg2lp2peO7yr" alt=""><figcaption><p>Using environment variables in Conditions or Aggregators</p></figcaption></figure> <figure><img src="/files/4ZNCeO2oNmA3uRt9LEY2" alt=""><figcaption><p>Using environment variables in Queries</p></figcaption></figure></div>

Then if you want to make it **110** instead of **100**, you can do it in one place, instead of changing all of your workflows and metrics.

For more information take a look at our video tutorial:

{% embed url="<https://youtu.be/BQoFwRUqyEA>" %}


---

# Agent Instructions: 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:

```
GET https://docs.ylem.co/pipelines/environment-variables.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
