> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/transformation-etl/matillion/configure-matillion-project-variables.md).

# Configure Matillion Project variables

If your Matillion project make use of [Project Variables](https://docs.matillion.com/data-productivity-cloud/designer/docs/variables/), consider configuring this entry in the Euno Matillion Integration.

By configuring project variables, Euno will substitute any reference to `${PROJECT_VARIABLE}` with its configured value.

For example, if you are using Project Variables to store the target schema for a Matillion pipeline, and you are making use of that Project Variable in your "Write Table" Matillion nodes, then Euno will only be able to observe the target table and its relationship with the pipeline if you configure the value of Project Variable in Euno.

This configure is done in the Matillion integration configuration screen, under "advanced".

The configuration expects a JSON object, where each entry is a project variable. For example, if your project variables are called `foo_db` and `foo_schema` and their values are `bar_db` and `bar_schema` respectively, enter:

```
{
    "foo_db": "bar_db",
    "foo_schema": "bar_schema"
}
```

## Using a pipeline to extract all Project Variables

In case you have many Project Variables, it might not be feasible to manually configure each one. Instead, follow these steps to extract them all:

1. In Matillion Designer, create a new "Orchestration" pipeline
2. Add a single node of type "python script".
3. Under the "script", configure:

```
SYSTEM_VARIBLES={'__name__', '__doc__', '__package__', '__loader__', '__spec__', '__builtins__', '__file__', '__cached__', 'io', 'os', 'redirect_stdout', 'traceback', 'json', 'SimpleNamespace', '__loadObject', 'ScriptContext', 'processDPCUser', 'context', 'sysvar'}

local_variables = [x for x in globals().keys() if x not in SYSTEM_VARIBLES]
local_vars_with_value = {x: str(globals()[x]) for x in local_variables}
print(json.dumps(local_vars_with_value))
```

4. Run the pipeline
5. Open the run, and expand the message. The result is a properly parsed JSON with variable configuration, which you can then copy into the Euno configuration field.


---

# 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.euno.ai/sources/transformation-etl/matillion/configure-matillion-project-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.