Files/Folders

This documentation describes the process of configuring and using the Files/Folders Watcher trigger on the platform. This trigger allows monitoring changes in specific files or directories, automatically starting bot execution when such changes are detected.

What is the Files/Folders Watcher Trigger?

The Files/Folders Watcher trigger is a functionality that continuously monitors a specific file or directory for changes, such as creation, modification, or deletion of files. When a change is detected, the trigger initiates the execution of a previously configured bot to handle that change.

Trigger Configuration

To configure this type of Files/Folders Watcher trigger, follow the steps below:

1. Navigate to https://sinfonia.live/watchers and select the option for New Watcher.
2. Choose between the 2 types of triggers Folder or File.

Trigger 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.

Bot

• Default value: First from the list of available bots
• Description: Bot that will be executed when the trigger is fired.
• Important: The bot must be previously created and available on the platform for selection.

Version

• Expected value: X.Y.Z (example: 1.0.0)
• Description: Specific version of the bot to be used.
• Important: There is an option to select the bot’s release version, which will always use the latest available version.

Label

• Description: Optional identifier for the trigger. Can be used for organization or filtering.

Agent

• Current value: Select an agent from the list
• Description: Defines the agent responsible for bot execution.
• Important: The agent must be active and connected to make selection during scheduling. Possibility to define multiple agents for the same schedule, avoiding execution bottlenecks.

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: true or false.

Folder path

• Description: Defines the directory to be monitored.
• Example: C:\Users\@user\Downloads\

Parameters (JSON)

• Description: Allows entering additional parameters for the bot, in JSON format.
• Example:

{
    "arg1": "1366",
    "arg2": "768"
}

File

The File type is used to monitor a specific file. Whenever this file is created or modified, the configured bot will be triggered.

Bot

• Default value: First from the list of available bots
• Description: Bot that will be executed when the trigger is fired.

Version

• Expected value: X.Y.Z (example: 1.0.0)
• Description: Specific version of the bot to be used.

Label

• Description: Optional identifier for the trigger. Can be used for organization or filtering.

Agent

• Current value: Select an agent from the list
• Description: Defines the agent responsible for bot execution.

File path

• Description: Defines the specific file to be monitored.
• Example: C:\Users\@user\Downloads\file.txt
• Supported file types: xls, xlsx, xlsm, txt.

Parameters (JSON)

• Description: Allows entering additional parameters for the bot, in JSON format.
• Example:

{
    "arg1": "1366",
    "arg2": "768"
}

Description

• Description: Field to provide a detailed description of the trigger, facilitating identification and understanding of its purpose.