# WATCHFOLDER

The watchfolder trigger will activate as soon as a new asset is detected within an active watchfolder. To use an watchfolder stream, it is mandatory to create a profile beforehand.

To enhance your workflow further, contemplate integrating a [Prestream](/helmut4-releases/helmut4-components/helmutio/streams/io-event-triggers/prestream.md) within the Watchfolder profile. 

{% hint style="warning" %}
While the watchfolder job is carried out by a client, it is imperative for the Helmut server to have access to the content of the specified watchfolders.

This is crucial because the ***IO container*** consistently monitors for any newly incoming assets.
{% endhint %}

For more information about how to set up a watchfolder see: [Watchfolder](/helmut4-releases/helmut4-components/helmutio/wachfolder.md)

### Host Assignment

{% hint style="warning" %}
Any stream with this trigger must have "CLIENT" as the host type. Since this stream needs to be assigned to any user/client, server execution is not possible.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.helmut.de/helmut4-releases/helmut4-components/helmutio/streams/io-event-triggers/watchfolder.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.