> 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-reader/read-files-in-a-folder.md).
# How to read files inside a folder
Learn how to read files using File Reader connector on the Digibee Integration Platform.
Let's say you have a file named `"file.txt"` inside `"folder"`, available in your pipeline.
To read this file inside a folder, you may use a **File Reader** that indicates the path "folder/file.txt". That way, you can access the file 'file.txt'.
Follow the steps below to learn how to do it:
1. Create a pipeline and add a **File Reader**.
2. Open the configuration form of the connector.
3. Define the **File Name** parameter as `"folder/file.txt"`.
4. Click **Confirm** to save the connector settings.
5. Connect the trigger to the **File Reader***.*
6. Run a test in the pipeline (CTRL + ENTER).
The result will be shown:
```json
{
"data": [
"my sample content"
],
"fileName": "folder/file.txt",
"lineCount": 1
}
```
* **data:** array with the content of the file read by **File Reader***.*
* **fileName:** shows the complete path of the read file.
* **lineCount:** identifies the amount of lines within the file read by **File Reader***.*
---
# 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 dynamically 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-reader/read-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 `build a script that syncs our docs to a CMS` 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.
