> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/equipme/automation/workflows/using-variables-to-map-data.md).
# Using Variables to map data
In automation systems, variables are critical placeholders for data that is only available at runtime. These dynamic elements represent information from one source component and can be utilized in other connected components throughout a flow. Variables allow you to capture and carry data that will only be known during the flow's operation, enhancing connectivity and efficiency in processes. Let's explore their functionality through a practical example from an order fulfillment system.
**Example Scenario: Email Notification for New Orders from Important Customers**
You want to ensure a high-quality service experience for key customers by setting up a system to receive immediate email notifications when these customers place new orders. The aim is to closely monitor these transactions to ensure that everything proceeds smoothly and any potential issues are promptly addressed.
**Trigger Component:**
* **NewFulfillmentOrder**: This component is triggered whenever a new order is placed. It captures all necessary details about the order, including the customer's name, order ID, and the total purchase price.
* **SendEmail**: Configured to send an email notification whenever an order from a VIP customer is detected. Variables are employed to personalize the email content.
When building a flow in Equipme, you will see a Variables picker on the right side of the screen. This tool displays all the available variables that can be utilized at the current step of the flow. To ensure you receive the needed order details in your email, you will:
By picking these relevant variables, you ensure that every time a new order is triggered by one of your VIP customers, the email you receive contains all the essential details: who ordered, what they ordered, and the price of the service they ordered. This information helps you to quickly assess the order's importance and urgency, allowing for immediate and appropriate action.
Initially, we specify which customers should trigger notifications through the use of variables. So, who are our VIPs? In this case, we have selected two valuable customers, Beta GmbH and Omega Corp, to ensure we're promptly informed about their orders.
In this example, the primary goal is to receive detailed information about each new order placed by key customers. Specifically, you want to know which customer placed the order, what items were ordered, and the total price of the order. To achieve this, you'll use the Variables picker within Equipme to select and map the relevant variables.
Notice that we've used the Variables picker on the right to show available variables. This icon and, most importantly, the variable feature is available to you any time you create a flow. Thus, you can map data between any pre-built apps and utilities, or any other component that you build yourself.
---
# 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:
```
GET https://hub.equipme.io/equipme/automation/workflows/using-variables-to-map-data.md?ask=
```
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.