> 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/folder-delete-action.md).

# Folder Delete Action

The **Folder Delete Action** node deletes one or more folders from the file system.

The specified directories can be removed even if they contain files and subfolders, depending on the configured behavior. The operation is performed on the host system where the stream is executed (client or server).

#### Input Parameters

**Folder Path**\
List of folder paths (including folder names) that should be deleted.

**Not Empty**\
Defines how the node behaves if the folder contains files or subfolders:

* **DELETE\_ANYWAY** — delete the folder and all its contents recursively
* **SKIP** — leave the folder unchanged and continue the workflow
* **FAIL** — stop the node with an error

<figure><img src="/files/9HJEQq66LWOAt05uc8WT" alt="" width="352"><figcaption><p>Folder Delete Action</p></figcaption></figure>

#### Behavior

* Deletes entire directories
* Can remove folders recursively with all contents
* Processes multiple folders in a single execution
* Supports asynchronous execution

#### Typical Use Cases

* removing project working directories
* cleaning temporary processing folders
* archive housekeeping workflows
* deleting failed job outputs
* resetting watchfolder environments

#### Important Note

Using **DELETE\_ANYWAY** permanently removes the folder and everything inside it.\
The deletion bypasses any recycle bin or trash functionality provided by the operating system.

#### Practical Tip

This node is typically used at the end of automated workflows to remove working directories after delivery, archiving, or transfer has successfully completed.


---

# 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/folder-delete-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.