> 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/connectors/files/file-writer/write-files-in-a-folder.md).
# How to write files inside a folder
Learn the write files using the File Writer connector on the Digibee Integration Platform.
Let's say you have a file named `"file.txt"` inside `"folder"`, available in your pipeline.
To write this file inside a folder, you may use a **File Writer** that indicates the path `"folder/file.txt"`. That way, you can access the file `"file.txt"`.
Check how to do that:
1. Create a pipeline and add a **File Writer**.
2. Open the configuration form of the connector.
3. Define the **File Name** parameter as `"folder/file.txt"`.
4. Define the **Data** parameter as `{{ message.data }}`*.* Mind we're using the Double Braces expression*:* `{{ message.data }}` to access the result of the last component. In this case, we access `data` with the content of the file to be written.
5. Click **Confirm** to save the connector settings.
6. Connect the trigger to the **File Writer**.
7. Run a test in the pipeline (CTRL + ENTER).
The result will be shown:
```json
{
"fileName": "folder/file.txt",
"success": true
}
```
* **fileName:** shows the complete path of the written file.
* **success:** when the result is "true", it indicates that the execution was successful.
---
# 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/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.
