> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/integrations/flows/data-operations/object-handling/practical-example-handling-variables.md).
# Practical example: Handling variables
### Context**:**
Let's imagine a flow where the objective is to receive a list of guests and validate that the guest and their possible companion are authorized to enter the party.
Entry data:
```json
[
{
"nome": "João",
"idade": 24,
"cep": "00000-000",
"subConvidado": {
"nome": "Júlia",
"idade": 34,
"cep": "22222-222"
}
},
{
"nome": "Pedro",
"idade": 57,
"cep": "11111-111"
}
]
```
Business rule:
The flow will hit a REST CLIENT passing the name and age information for data validation. If there are companions, it will fall into a branch of the flow.
From this point on, let's assume that the *element* is the following object
```json
{
"nome": "João",
"idade": 24,
"cep": "00000-000",
"subConvidado": {
"nome": "Júlia",
"idade": 34,
"cep": "22222-222"
}
}
```
Within the Festa.io module, we'll configure it as follows:
Where "nome" and "idade" are operation parameters and we will fill in this information via the element parameter by specifying the "Path" within each operation parameter.
Using the IF module, we will check for the existence of a companion for the guest.
We can see that variable 1, from the first condition, also refers to the element parameter, but now the property we are interested in is called "subConvidado". Knowing this, we define the path as shown in the image:
At this point, we have already configured the validation of user information for the Festa.io module and we have also validated the existence of a companion for different approaches within the same flow.
The other modules not detailed in the example follow the structure and logic of those already detailed in this article.
***
---
# 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.skyone.cloud/english/skyone-studio/integrations/flows/data-operations/object-handling/practical-example-handling-variables.md?ask=&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.
.png)
