> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/dynamic-variables-in-flow.md).

# Insert dynamic variables in a flow

Use a flow variable as data in a document

## Insert dynamic variables in a document

Sometimes you need to display one or more dynamic values when generating a document.

**In a Salesforce flow:**

### Create a collection variable

Start by creating a collection variable in your flow. This variable will store the data you want to display in your document.

### Assign values to the collection variable

Add an Assignment element to assign the desired values to the collection variable. The order of the assignments determines the order of the tags to place in the document.

### Fill in the collection variable in the generation action

In the document generation action, enable the "Collection of Dynamic Values" parameter, then enter the collection variable used previously.

### Place the tags in the document

In your document template, place the Gonexa tags to display the dynamic values at generation.

**The dynamic tag**

The `{!gnxdynamic|1}` syntax displays the **Nth** value of a collection variable

**Parameters:**

* **N** = index of the desired value (starts at 1)

{% hint style="success" %}
**Example**

With a collection variable containing "Paris, Lyon, Marseille, Bordeaux", `{!gnxdynamic|2}` displays the second value in the list, which is Lyon
{% 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://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/dynamic-variables-in-flow.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.