Files and Folders
Use the files and folders trigger (Watcher) when a bot must react to a file arriving or changing, for example processing every PDF saved to an inbox folder. The watcher runs on the selected agent: it monitors the configured path and triggers the bot whenever it detects a change, such as a file being created or modified.
Registered Watchers
The watchers screen lists every configured monitor.
| Column | Description |
|---|---|
| Bot | Bot executed when the watcher fires. |
| Version | Bot version specified for execution. |
| Mode | Execution mode (headless, parallel, headed). |
| Agent | Agent responsible for monitoring. |
| Path | Path of the monitored folder or file. |
| Status | Whether monitoring is active or inactive. |
| Actions | Icons to edit or remove the watcher. |
New Watcher
To configure this type of Files/Folders Watcher trigger, follow the steps below:
- Navigate to https://sinfonia.live/watchers and select the option for
New Watcher. - Choose between the 2 types of triggers
FolderorFile.
Watcher Types
There are two types of configurations for the Watcher:
- Folder: Configuration for monitoring files in a specific folder.
- File: Configuration for individual file monitoring.
Folder
The Folder type is used to monitor all files with a specific extension within a folder. Whenever a file with the defined extension is created or modified, the configured bot will be triggered.
| Field | Description | Notes |
|---|---|---|
| Bot | Bot that will be executed when the trigger is fired. | Must be previously created and available on the platform for selection. |
| Version | Specific version of the bot to be used. | Accepts X.Y.Z (example: 1.0.0) or release, which always uses the latest available version. |
| Label | Optional identifier for the trigger. | Can be used for organization or filtering. |
| Agent | Defines the agent responsible for bot execution. | The agent must be active and connected. Multiple agents can be selected, avoiding execution bottlenecks. |
| Parameters (JSON) | Additional parameters sent to the bot, in JSON format. | Reach the code as environment variables. Example: {"arg1": "1366", "arg2": "768"} |
| Description | Free text describing the trigger’s purpose. | Makes it easier to identify on listing screens. |
Extension
- Description: Defines the type of file that will be monitored (extension).
- Available values:
pdf,txt,docx.
Recursive
- Description: Indicates whether monitoring will be performed recursively in subfolders.
- Available values:
trueorfalse.
Folder path
- Description: Defines the directory to be monitored.
- Example:
C:\Users\@user\Downloads\
File
The File type is used to monitor a specific file. Whenever this file is created or modified, the configured bot will be triggered.
| Field | Description | Notes |
|---|---|---|
| Bot | Bot that will be executed when the trigger is fired. | Must be previously created and available on the platform for selection. |
| Version | Specific version of the bot to be used. | Accepts X.Y.Z (example: 1.0.0) or release, which always uses the latest available version. |
| Label | Optional identifier for the trigger. | Can be used for organization or filtering. |
| Agent | Defines the agent responsible for bot execution. | The agent must be active and connected. Multiple agents can be selected, avoiding execution bottlenecks. |
| Parameters (JSON) | Additional parameters sent to the bot, in JSON format. | Reach the code as environment variables. Example: {"arg1": "1366", "arg2": "768"} |
| Description | Free text describing the trigger’s purpose. | Makes it easier to identify on listing screens. |
File path
- Description: Defines the specific file to be monitored.
- Example:
C:\Users\@user\Downloads\file.txt - Supported file types:
xls,xlsx,xlsm,txt.
Edit Watcher
To edit an existing watcher, click the edit icon in the Actions column. The fields are the same as in creation, described in New Watcher.
Remove Watcher
To remove a watcher, click the trash icon in the Actions column.
Tip
A confirmation modal will be requested.