> 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-guides/file-and-folder/get-file-list.md).

# Folder get file list

Folder get file list is the action used to scan a directory on the computer and collect all the paths of the files present in that directory, then store them all in an array in the output variable.

This action is extremely useful when you have a directory containing many images, videos, or configuration files and want to retrieve that list to process each file one by one in a loop, or to count how many files are currently in the directory.

> 🔗 See the detailed guide on how to combine this action to count the number of files and check conditions in section [2. Count the number of files in a directory (Folder)](/automate-en/action-guides/variables/count.md#vi-du-thuc-te-dem-so-luong-anh-bat-dong-san-trong-thu-muc-d-bds-cat-bi) in the Count section.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gpmautomate.com/automate-en/action-guides/file-and-folder/get-file-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.