> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/file-and-folder-22/get-files-from-folder-action.md).

# Get Files From Folder Action

The **Get Files From Folder Action** node iterates over all files located in a specified folder and passes each file path to the stream.

The folder can be scanned either only at the top directory level or recursively including all subdirectories, depending on the node settings.

For each discovered file, the node triggers the following nodes once and writes the current file path into the wildcard:

[{job.source}](/helmut4-releases/helmut4-components/streamdesigner/wildcards/job-related-wildcards-32/job-source.md)

This allows subsequent nodes to process each file individually.

***

#### Input Parameters

**Folder Path**\
Path to the folder that should be scanned.

**Scan Recursively**\
If enabled, all subfolders are included in the scan.\
If disabled, only files located directly inside the specified folder are processed.

<figure><img src="/files/YCELBsjG0XGiPqZrgqVc" alt="" width="354"><figcaption><p>Get Files From Folder Action</p></figcaption></figure>

#### Behavior

* Searches the specified directory for files
* Iterates once per discovered file
* Writes the current file path to [{job.source}](/helmut4-releases/helmut4-components/streamdesigner/wildcards/job-related-wildcards-32/job-source.md)
* Continues until all files have been processed
* Supports asynchronous execution

#### Typical Use Cases

* watchfolder ingest workflows
* batch transcoding
* automated file validation
* bulk metadata processing
* migration or archive preparation

#### Practical Note

This node effectively converts a folder into a loop.\
Instead of manually selecting files, the workflow automatically processes every file inside the directory one after another.


---

# 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.helmut.de/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/file-and-folder-22/get-files-from-folder-action.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.