> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/file-and-folder/file-read-all-text.md).
# File read all text
File read all text is an action used to read the entire content of a `.txt` formatted text file at once. All the data inside the file will be returned as a single string and stored in an output variable.
🎥 Watch the tutorial video: [Here](https://youtu.be/EH7olDLAb9c).
#### Configuration parameters:
* File Path: The absolute path to the `.txt` file to be read (For example: `D:\data\content.txt`).
* Output variable: The name of the variable that stores the structure of the read string.
#### Practical example: Reading the content of a prepared article
Suppose you have prepared a long article (consisting of multiple sentences, line breaks, and whitespace) stored in the text file `D:\GPM\post.txt`. You want to retrieve all this content to automatically fill in the post field on the browser:
* Configuration:
* File Path: Enter the path `D:\GPM\post.txt`
* Output variable: Name the variable that stores the result as `$textContent`.
* Result: The system will capture all characters and line structures in the file and assign them to the variable `$textContent`. In the next steps, you just need to call the Key press action passing this `$textContent` variable into the input field of the website.
---
# 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.gpmautomate.com/automate-en/action-guide/file-and-folder/file-read-all-text.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.
