# Variable Portal
The [Variable Portal](/dev-tooling/blocks/base-variable/variable-portal.md) block enhances the flexibility and organization of our graphs, allowing for more efficient data transfer and management.
`Variable Portal` blocks are not essential, and are never actually necessary, since it would always be possible to link your data directly from a block's output to another block's input, without first passing the data through a `Variable Portal` block. The point of `Variable Portal` blocks, then, is simply to keep your graph visually organized, and to prevent your dotted-line connections from crossing through areas of your graph that are already complicated, making things more confusing to look at. The following graph uses a Telegram bot to listen for the command "/maticprice", and to respond with a message containing Matic's price in whatever channel it heard the command:
The `Variable Portal` blocks in this example are receiving references to the Telegram channel and Telegram bot that heard the command and then passing those references along to the `Send Telegram Message` block at the end of the graph, so that the reply is made by the same bot and in the same channel as the command occurred.
We could simply skip the `Variable Portal` blocks and instead pass that data directly from the `Telegram Bot` and `On Telegram Message` blocks to the `Send Telegram Message` block. The consequence of this would be that those two dotted white lines would pass through the middle of all our other blocks, making our graph more visually confusing.
---
# Agent Instructions: 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://docs.graphlinq.io/dev-tooling/blocks/base-variable/variable-portal.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.
