> For the complete documentation index, see [llms.txt](https://docs.floui.io/guia/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.floui.io/guia/conectores/categorias/manipulacao-de-dados/template.md).

# Template

Defina um template (modelo) para tratar informações geradas na execução do fluxo.

{% tabs %}
{% tab title="Parâmetros" %}

<figure><img src="https://215079342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F226k0cnPTn1PWu9xHcK8%2Fuploads%2F2etV1XSF9tntze7I9GCf%2Fimage.png?alt=media&amp;token=b59628f1-cd97-4281-948a-78aa681c83a1" alt="" width="375"><figcaption><p>Parâmetros de configuração</p></figcaption></figure>

<table><thead><tr><th width="189">Campo</th><th width="128">Tipo</th><th>Descrição</th></tr></thead><tbody><tr><td>Descrição</td><td>Campo de texto</td><td>Elemento visual usado para descrever a funcionalidade do conector dentro do fluxo. </td></tr><tr><td>Conteúdo do template</td><td>Campo de texto</td><td>Aceita um objeto Javascript completo. Permitindo manipular dados que estão em memória durante a execução do fluxo através do objeto msg.</td></tr><tr><td>Converter conteúdo</td><td>Seletor</td><td>Este atributo permite definir se a saída do conector será uma string ou um objeto Javascript já convertido.</td></tr><tr><td>Output path</td><td>Campo de texto</td><td>Define o nome de um atributo que irá armazenar a saída de dados do conector dentro do objeto msg no contexto do fluxo atual.</td></tr></tbody></table>
{% endtab %}

{% tab title="Payload" %}

## Sucesso

Por padrão, o conector permite que as saídas sejam em formato string ou já convertidas para objeto Javascript.

<figure><img src="https://215079342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F226k0cnPTn1PWu9xHcK8%2Fuploads%2FgR35CezBUKVhrzC1TNLr%2Fimage.png?alt=media&amp;token=e07fd2f5-6c5f-4ede-a214-04ed862fb68b" alt=""><figcaption><p>JSON já convertido para objeto Javascript.</p></figcaption></figure>

<figure><img src="https://215079342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F226k0cnPTn1PWu9xHcK8%2Fuploads%2FnkWpCbXmhapBExQTFIEX%2Fimage.png?alt=media&amp;token=1cd9c35d-6365-498f-a49b-55f9747ff430" alt=""><figcaption><p>Conteúdo em formato JSON String.</p></figcaption></figure>
{% endtab %}
{% endtabs %}


---

# 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.floui.io/guia/conectores/categorias/manipulacao-de-dados/template.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.
