> For the complete documentation index, see [llms.txt](https://help.filestar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filestar.com/automation/trigger-folders.md).

# Trigger Folders

{% hint style="info" %}
Trigger Folders are currently only available on Windows.
{% endhint %}

<figure><img src="/files/Jn1XnNsztv4YCMTGiuS6" alt=""><figcaption></figcaption></figure>

With trigger folders, you can run a recipe on any file that is dropped in a specified folder.

For this to work, a small lightweight application called ‘FilestarAgent.exe’ needs to run on your computer. The agent monitors file changes in your trigger folders and initiate the conversions. When you create your first trigger folder, Filestar will make sure that this application is started when rebooting your computer. You can know that the agent is running if you can see the Filestar icon in your system tray.

After you have run a skill you will see a button called ‘Automate’, clicking on this exposes a menu where one of the options is to create a new trigger folder. This will open the window seen in the image above.

If you select ‘Run in Background’, Filestar will run the entire process in the background and only communicate through notifications.

Files that Filestar produces and saves in a trigger folder does not trigger a conversion.


---

# 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://help.filestar.com/automation/trigger-folders.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.