> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/docs/fr/actions/grids/run-workflows-in-grid/map-workflow-outputs.md).

# Associer les sorties du workflow

### Mappage des sorties du workflow vers une nouvelle colonne

Le mappage des sorties de vos exécutions de workflow directement dans la grille vous aide à les afficher et à les modifier efficacement. Une fois qu’un workflow a été exécuté avec succès, vous pouvez mapper ses sorties en :

* Cliquez sur l’icône d’extension sur la cellule du workflow (elle devrait indiquer « Réussite »)
* Pour ajouter une seule sortie comme colonne de grille :
  * Survolez l’élément du workflow que vous souhaitez mapper à une nouvelle colonne
  * Cliquez sur « Ajouter à la colonne »
* Pour ajouter toutes les sorties comme colonnes de grille :
  * Cliquez sur « Ajouter en colonnes séparées »

Cet élément de la sortie du workflow est maintenant automatiquement ajouté en tant que nouvelle colonne à votre grille actuelle. Le type de colonne sera automatiquement assorti au type de format de la sortie.

{% @arcade/embed url="<https://app.arcade.software/share/SSS6zbUdFBiBKY5Yf5pf>" flowId="SSS6zbUdFBiBKY5Yf5pf" %}


---

# 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://docs.airops.com/docs/fr/actions/grids/run-workflows-in-grid/map-workflow-outputs.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.