> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/tips-and-tricks/create-a-variable-and-use-it-in-a-component-property.md).

# Create a variable and use it in a component property

## Overview

A Component attribute can be set into a variable to set this attribute as a common value wherever it's used in your flow.

## Steps

### 1. Create a variable resource

* Create a variable resource
* Enter an **API Name**
* For the Data Type field, select **`Text`**
* Type the Attribute value in the Default Value field and "Done"

{% @arcade/embed url="<https://app.arcade.software/share/dfaTGJnIy35WzdKc8l8i>" flowId="dfaTGJnIy35WzdKc8l8i" %}

### 2. Add the variable resource to your flow screen component

* Click on the component you want to create a variable to
* Open the Component Builder
* Select the Attribute where you want to associate your variable
* Select **`Mapped`** as a display option to access your flow variables
* Select your variable
* Click "**`Done`**" to save

{% @arcade/embed url="<https://app.arcade.software/share/cn8St5J4yUWDzs3SYyZJ>" flowId="cn8St5J4yUWDzs3SYyZJ" %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.avonnicomponents.com/flow/tutorials/tips-and-tricks/create-a-variable-and-use-it-in-a-component-property.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.