> 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/tag-generations-in-log.md).

# Tag each generation in the log

Tag each generation to better track and manage post-generation actions.

## Set a variable in the generation actions

Sometimes you need to create automations after a document is generated, such as sending it by email or for signature.\
In a Salesforce flow, you can identify each generation and find this information in the generation log.

**In a Salesforce flow:**

### Add the generation action

* Fill in the usual expected parameters
* Enable the "Generation Tag" parameter
* Enter a descriptive value in this field, such as the flow name or any information that clearly identifies the generation in the generation log.

{% hint style="danger" %}
**Warning**

The text is limited to 255 characters
{% endhint %}

* Save your flow
* When a document is generated through this flow, the "Generation Tag" field in the generation log automatically takes the defined value

With this information in the generation log, you can then easily define the trigger conditions of your automations.


---

# 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/tag-generations-in-log.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.