🇬🇧 EN

🗂️ Local File Watch

Monitors a directory on the server's filesystem for new files using filesystem events. Fires a workflow run each time a new file is detected. Useful for processing files written by other services on the same machine.

Category: Triggers · Type identifier: local_file_watch

Overview

The Local File Watch trigger listens to filesystem events on the server where Flusso is running. When a new file is created in the configured directory, Flusso immediately fires a workflow run with the file's details as output variables. Unlike cloud-based file triggers, this node does not poll — it reacts to filesystem notifications in near real time.

This is the right trigger when other services on the same server produce output files: a legacy export job writes CSVs to a directory, an FTP server receives incoming uploads, or a script generates reports on a schedule. Instead of wrapping those services in a new integration, you simply point the Local File Watch at the directory and let Flusso react.

The Flusso process must have read access to the configured directory. If the Move After Processing option is enabled, it also requires write access to create the processed/ subdirectory.

Configuration

Field	Status	Description
Directory Path	Required	Absolute path on the server, e.g. `/var/data/incoming`. The Flusso process must have read access to this path.
Pattern	Optional	Glob pattern to match, e.g. `.csv`. Default: `` (all files).
Move After Processing	Optional	Toggle. When enabled, move the file to a `processed/` subdirectory after the workflow run starts to prevent duplicate triggers.

Output Data

Each workflow run triggered by this node receives the following fields describing the newly detected file.

Field	Type	Description
`file.path`	string	Absolute path to the new file
`file.name`	string	Filename with extension
`file.size`	number	File size in bytes
`file.detected_at`	string	ISO 8601 timestamp when the file was detected

{{ trigger.output.file.path }} {{ trigger.output.file.name }} {{ trigger.output.file.size }} {{ trigger.output.file.detected_at }}

Example Usage

Watch /var/exports/ for new .csv files dropped by a legacy system, then parse and import the data.

Add a Local File Watch trigger. Set Directory Path to /var/exports, set Pattern to *.csv, and enable Move After Processing to prevent re-processing.
Add an HTTP Request node. Use {{ trigger.output.file.path }} in the request body to tell your import service which file to read.
Add an Email Notification node to alert the team when an import completes. Include {{ trigger.output.file.name }} in the message body.

Tips & Notes

Near real-time detection. Unlike polling-based triggers, Local File Watch reacts to filesystem events. Detection typically happens within a second of file creation.
Avoid watching high-volume directories. If a directory receives thousands of files per minute, each file will start a workflow run. Use a pattern filter to narrow the scope.
Use Move After Processing to prevent duplicates. Without it, a file that is slowly written (e.g. large uploads) may trigger multiple events. Moving the file once the run starts ensures each file is processed exactly once.
The directory must exist before activating the workflow. Flusso does not create the directory. If the path does not exist when the workflow is activated, the trigger will fail to start.
Temporary files may trigger the workflow. Some applications write to a temp file and rename it. Use a pattern filter (e.g. *.csv) to avoid false triggers on .tmp files.

Related Nodes

Google Drive Watch — watch a folder in Google Drive.
Dropbox Watch — watch a folder in Dropbox.
HTTP Request — call external APIs after detecting a file.