> 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-lines.md).

# File read all lines

File read all lines is an action used to read a `.txt` text file and automatically split each line in the file into a separate element, then store all of them in an output array.

This action is extremely useful when you have a list of data arranged line by line (such as a proxy list, keyword list, 2FA code list...) and want to use a loop to process each line one by one.

🎥 See more tutorial video: [Here](https://youtu.be/EH7olDLAb9c).

> 🔗 See detailed instructions on how to use in the example [1. Count the number of lines in a text file (Text)](https://docs.gpmautomate.com/automate-en/action-guide/file-and-folder/pages/dThT2mFKvBR6wL42asdx#vi-du-thuc-te-dem-so-luong-link-facebook-trong-file-d-2.txt) in the Count*)*.


---

# 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-lines.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.