File System Trigger
A file system trigger watches a folder on a robot's machine and runs a flow when a file appears, changes or is removed. It is the usual way to automate "someone drops a file in here".
Triggers are created in Admin Console → Triggers, with Add Trigger.
1. Trigger Type
Pick the File System category, then one of three events:
| Trigger | Fires when |
|---|---|
| File Created | A file appears in the folder |
| File Deleted | A file is removed |
| File Modified | An existing file changes |
2. Details
Give the trigger the directory path to watch and a file name to match.
The file name is a pattern, not a literal. Use .* to match anything in the folder, or
something like .*\.csv for one kind of file.
3. Flow & Details
Name the trigger, then choose the published flow to run, its version, and the robot that will watch the folder.
The robot watches its own filesystem. A path that exists on your laptop means nothing to a robot on a server — this is the most common reason a file system trigger never fires.
The robot has to be connected for a trigger to fire. A trigger on an offline robot is not queued; the event is simply missed.