> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/development/flow-studio/applications/menu/inbox/public-variables.md).

# Public variables

Public Variables are visible from outside the current workflow, and are used to provide instance-specific information when configuring the template for an Inbox.

To create public variables:

1. Navigate to metadata in the workflow.
2. Open the panel for public variables.
3. Create a new public variable.
4. Choose a name for the new public variable.
5. Confirm and create the new variable.

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-onOWJmJDlgONGcw8O%2F-M-oo3n316aj6prHLEcH%2Fhelp_root_applications_pubvar.PNG?alt=media\&token=ba384306-81bc-47d2-a4b3-0babe7b554de)

To assign a value to the public variable:

1. Navigate to Workflow->Public Variables in the main menu. 
2. Click on public variables.
3. Select your public variable and map it to a system variable.
4. Press ok to save changes.

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-onOWJmJDlgONGcw8O%2F-M-oo7mqkWVRrk-HETfu%2Fhelp_root_applications_mapvar.PNG?alt=media\&token=2710ef46-41dd-43db-903b-432b4b15cf68)

{% hint style="info" %}
Read more about [inboxes](/6.12/development/flow-studio/applications/menu/inbox.md)
{% endhint %}


---

# 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.novacuraflow.com/6.12/development/flow-studio/applications/menu/inbox/public-variables.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.