> For the complete documentation index, see [llms.txt](https://docs.zaia.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zaia.app/workflows/workflow-nodes/variables-node.md).

# Variables Node

The **Variables** node allows you to define, store, and reuse values throughout your Workflow.\
It works like a **temporary memory** where you can save data from one step and use it later in another.

***

### 🛠️ How It Works

* You **map a variable name** (e.g., `productSKU`, `userEmail`, `city`).
* You **assign a value** to that variable. The value can come from:
  * Static text (you write it directly).
  * A **reference** to data produced by another node in the Workflow.
  * AI-generated content (if you enable **Use AI**).
* Once saved, the variable can be used in any following node.

***

### ⚙️ Configuration Options

* **Mapping name** → the variable’s key (e.g., `customerName`).
* **Value** →
  * Literal value (e.g., `"São Paulo"`).
  * Workflow reference (e.g., `@workflow.request.userInput`).
  * AI-generated (if you select **Use AI**).
* **Multiple variables** → you can add as many mappings as needed.

***

### 📌 Example Use Cases

* **Dynamic API Calls**\
  Save the user’s city into a variable `city` and use it in an HTTP Request node to fetch the weather:\
  `GET /weather?city=@workflow.variables.city`
* **Storing User Input**\
  Capture `name` and `email` once, then reuse them across different steps (e.g., CRM API, confirmation message).
* **AI Processing**\
  Enable **Use AI** to automatically transform or enrich the data before saving it (e.g., normalizing product names).

***

⚡ **Tip:** Variables make your Workflow **modular and reusable**, avoiding repeated inputs and allowing complex logic.