> 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/pt/acoes/grids/run-workflows-in-grid/map-workflow-outputs.md).

# Mapear resultados do workflow

### Mapear saídas do Workflow para uma nova coluna

Mapear diretamente na Grelha as saídas das execuções do seu Workflow ajuda-o a visualizá-las e editá-las de forma eficiente. Depois de um Workflow ter sido executado com sucesso, pode mapear as suas saídas da seguinte forma:

* Clique no ícone Expandir na célula do Workflow (deverá indicar "Sucesso")
* Para adicionar uma única saída como uma coluna da Grelha:
  * Passe o cursor sobre o elemento do Workflow que pretende mapear para uma nova coluna
  * Clique em "Adicionar à Coluna"
* Para adicionar todas as saídas como colunas da Grelha:
  * Clique em "Adicionar como Colunas Separadas"

Esse elemento da saída do Workflow é agora adicionado automaticamente como uma nova coluna à sua Grelha atual. O tipo de coluna será automaticamente correspondido ao tipo de formato de saída.

{% @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/pt/acoes/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.