> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/appmixer-studio-features/using-variables-to-map-data.md).

# Using Variables to map data

[In the previous section, you learned how to create Integration templates using the Wizard Builder feature](https://docs.appmixer.com/kb/appmixer-studio-features/creating-an-integration-template.md). Now, it's time to map data between different components using Variables.

{% embed url="<https://youtu.be/d8LfVsVMNEk>" %}
How to use Variables to map data?
{% endembed %}

Variables are placeholders for data that will be only known at flow runtime. They let you use data from one component in other - connected - components.&#x20;

For example, a component that triggers with new messages in a private Slack channel passes data to a component that sends SMS for each new message. In the SMS text, the original Slack message is passed using Variables.

![Mapping data between Slack and Twilio using Variables](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-MfC4v8O4Wdu5F2Ik3kN%2F-MfCAYjDnGt00EVWakkg%2Fgif-2-1.gif?alt=media\&token=10a7bc6e-5f90-450b-a006-369ed55d840b)

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.

Now that you know how to use variables to map data between different components, [let's see how you can alter the data using Modifiers](https://docs.appmixer.com/kb/appmixer-studio-features/using-modifiers-to-alter-data.md).


---

# 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.appmixer.com/kb/appmixer-studio-features/using-variables-to-map-data.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.
