> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/chat-flow/untitled-1.md).

# Referring to variables

Variables can be sourced from the session, HTTP calls, or user input. 

You can refer to these variables in other nodes in your workflow by wrapping them in double square brackets, e.g., ***\[\[Variable Name]]**.* 

For example, when using the [*Request Input* ](/chat-flow/user-facing-nodes/input-nodes/menu-nodes-ask-for-input.md)node or [*Multiple Choice Input*](/chat-flow/user-facing-nodes/branch-logic-split/menu-nodes-multiple-choice-input.md) node, you capture a user's input as a variable (you create this variable, and can decide on what to call it). Let's say you ask the user to enter their first name, and you use the variable name *FirstName* to store the user’s input. 

{% hint style="warning" %}
If you use identical variable names in more than one node and refer to that name in another node, the node for which a response was captured last will override the others that were captured before it.
{% endhint %}

{% embed url="<https://vimeo.com/761776445?share=copy>" %}

&#x20;See the example below:

![](https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/tq9wCRRHRX9MyASroYqJ/image.png)

When completing the information required for a node, you might sometimes see the following icon:

![](https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/YhX0ks7egXvO5uM9nmDa/image.png)

Clicking this icon brings up *Variables & Shortcuts.*&#x20;

This panel lists all variables that you have added in nodes across your flow and serves as a shortcut when you want to refer to any of these variables in your current node.&#x20;

![](https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/d4AkW8g5ZtXaAvlqCLLL/image.png)

To learn how to store and reference more complex variables that were retrieved via an API call, please watch the video below.

{% embed url="<https://vimeo.com/761776789?share=copy>" %}
To learn how to store and reference more complex Variables that were retrieved via an API call
{% endembed %}


---

# 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://help.clickatell.com/chat-flow/untitled-1.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.