> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/pt-br/connectors/files/file-writer/write-files-in-a-folder.md).
# Como escrever arquivos dentro de pastas
Saiba como usar o conector File Writer na Digibee Integration Platform.
Digamos que você tenha um arquivo `"file.txt"` na pasta `"folder"` disponível no seu pipeline. Para poder escrever esse arquivo dentro de uma pasta, você pode usar um **File Writer** que indique o caminho `"folder/file.txt"`. Dessa forma, você consegue acessar o arquivo `"file.txt"`.
Veja como fazer isso:
1. Crie um pipeline e adicione um conector **File Writer**.
2. Abra o formulário de configuração do conector.
3. Defina o parâmetro **File Name** como `"folder/file.txt"`.
4. Defina o parâmetro **Data** como `{{ message.data }}`*.* Note que usamos a expressão em Double Braces*:* `{{ message.data }}` para acessar o resultado do último conector. Nesse caso, acessamos `data` com o conteúdo do arquivo a ser escrito.
5. Clique em **Confirmar** para salvar as configurações do conector.
6. Conecte o trigger com o **File Writer**.
7. Execute um teste no pipeline (CTRL + ENTER).
O resultado será apresentado:
```
{
"fileName": "folder/file.txt",
"success": true
}
```
* **fileName:** apresenta o caminho completo do arquivo que foi escrito.
* **success:** quando apresenta *true* no resultado, indica que a execução foi bem sucedida.
---
# 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.digibee.com/documentation/connectors-and-triggers/pt-br/connectors/files/file-writer/write-files-in-a-folder.md?ask=&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.
