Skip to main content

Folder Monitor: Configure Directory Watching and Automated Responses

A folder monitor continuously watches specified directories for changes — new files, modifications, deletions, or renames — and triggers automated responses the moment something happens. DataMystic FileWatcher provides a visual folder monitor that handles everything from simple single-folder watching to complex multi-directory monitoring configurations with independent filters, actions, and schedules for each watched path.

What Is a Folder Monitor?

A folder monitor is software that observes one or more directories on your filesystem and detects when changes occur. Unlike manual checking — where someone periodically looks at a folder to see if anything new arrived — a folder monitor operates continuously and responds automatically. This is the foundation of file-based workflow automation: without reliable folder monitoring, no automated processing pipeline can function.

The folder monitor concept is simple, but production-quality implementations must handle numerous real-world challenges:

  • Incomplete files — Files still being written must not trigger processing prematurely
  • Network interruptions — Monitoring of network shares must recover gracefully from connectivity drops
  • High file volumes — The monitor must handle directories receiving hundreds of files per hour without missing any
  • Service operation — Monitoring must continue 24/7 without requiring a user to be logged in
  • Selective filtering — Only relevant files should trigger actions while others are ignored
  • Audit requirements — Every detection and action must be logged for compliance and troubleshooting

Setting Up a Folder Monitor with FileWatcher

FileWatcher makes folder monitor configuration straightforward through its visual interface. Each monitored directory is configured independently with its own settings:

Step 1: Choose the Directory to Monitor

Select any accessible directory for monitoring. FileWatcher supports local drives (C:\Incoming, D:\DataFeeds), mapped network drives (Z:\SharedFolder), and UNC paths (\\server\share\incoming). For network paths, specify credentials that FileWatcher will use to maintain access in Windows Service mode.

Step 2: Configure Subdirectory Behaviour

Choose whether the folder monitor watches only the specified directory or includes all subdirectories recursively. Recursive monitoring covers the entire directory tree below your selected path, automatically including newly created subdirectories as they appear.

Step 3: Set File Filters

Define which files the folder monitor should respond to. Use wildcard patterns to match specific file types or naming conventions:

  • Extension filters — *.csv, *.xml, *.xlsx, *.pdf to monitor specific file types
  • Name patterns — INVOICE_*.pdf, RPT_????????.txt to match naming conventions
  • Exclusion patterns — Ignore *.tmp, ~$*, Thumbs.db to filter out system and temporary files
  • Size thresholds — Minimum and maximum file sizes to exclude empty placeholders or anomalous files

Step 4: Select Event Types

Choose which file events the folder monitor should detect:

  • Created — New files appearing in the directory (most common trigger type)
  • Modified — Existing files being updated or rewritten
  • Deleted — Files being removed from the directory
  • Renamed — Files changing name or extension

Most automation workflows use the Created event to detect incoming files. Modification monitoring is useful for configuration file watching or data files that receive appended records.

Step 5: Configure Stability Settings

The folder monitor must distinguish between files that are still being written and files that are ready for processing. Configure stability settings to prevent premature triggering:

  • File age threshold — Wait until the file's last-modified time is at least N seconds in the past
  • Size stability — Verify the file size remains constant across consecutive polling cycles
  • File lock check — Attempt an exclusive open to confirm no other process holds the file

Step 6: Define Actions

Specify what happens when the folder monitor detects a qualifying event. Actions execute in sequence as a chain:

  • Move file — Relocate to a processing or archive directory
  • Copy file — Duplicate to backup or distribution locations
  • Rename — Apply naming conventions or add timestamps
  • Execute program — Run external applications like TextPipe, WordPipe, or custom scripts
  • FTP upload — Transfer to remote servers via FTP, FTPS, or SFTP
  • Email alert — Send notifications to stakeholders
  • Compress — Zip files for archival or transfer

Polling Intervals and Detection Speed

FileWatcher's folder monitor uses configurable polling to check directories for changes. The polling interval determines how quickly new files are detected:

  • 1-5 seconds — Near-instant detection for time-critical processing (real-time data feeds, urgent document routing)
  • 10-30 seconds — Recommended for most scenarios. Fast detection without excessive disk activity
  • 1-5 minutes — Low-overhead monitoring for batch scenarios where immediate detection is not critical

Each folder monitor can use a different polling interval, so time-sensitive directories poll aggressively while lower-priority paths use longer intervals to conserve resources.

Multi-Directory Folder Monitor Configurations

Real-world automation typically requires monitoring multiple directories. FileWatcher manages any number of folder monitors simultaneously, each with independent configuration:

  • Separate paths — Monitor different input directories for different data sources or departments
  • Different filters — Each folder monitor watches for its specific file types
  • Independent actions — Each monitored path triggers its own action chain
  • Different intervals — Prioritise polling speed per directory based on business requirements

This flexibility lets you build comprehensive monitoring topologies that cover all file-based inputs to your organisation without requiring multiple separate tools or services.

Network Folder Monitoring

Enterprise environments store files on network shares, NAS devices, and file servers. FileWatcher's folder monitor handles network monitoring reliably:

  • UNC path support — Monitor \\server\share\folder paths directly without drive mapping
  • Stored credentials — Save authentication details for network path access without depending on interactive login sessions
  • Connection recovery — Automatic reconnection after network interruptions without manual intervention
  • Latency handling — Polling-based approach works reliably regardless of network latency, unlike event-based approaches that can miss notifications over slow links

Folder Monitor as a Windows Service

For production deployments, the folder monitor must operate 24/7 without any user interaction. FileWatcher installs as a Windows Service, providing:

  • Automatic startup — Monitoring begins when the machine boots, before any user logs in
  • Session independence — Continues running through logoffs, user switches, and RDP disconnections
  • Crash recovery — Windows Service recovery settings restart the monitor automatically after unexpected failures
  • Resource efficiency — Runs with minimal memory footprint as a background service

Logging and Audit Trails

Every folder monitor action is logged with timestamps, file details, and outcome information. Logs provide:

  • Detection records — When each file was detected and which folder monitor matched it
  • Action results — Success or failure status for every action in the chain
  • Error details — Specific error messages and context when actions fail
  • Performance data — Processing time per file for capacity planning

This logging is essential for compliance environments, troubleshooting, and operational visibility into your automated workflows.

Folder Monitor Use Cases

  • Data feed processing — Monitor for incoming CSV/XML data feeds and trigger validation and transformation pipelines
  • Document automation — Watch for new Office documents and trigger batch processing with Office Pipe tools
  • Report distribution — Detect generated reports and automatically distribute via FTP, email, or file copy
  • Backup automation — Monitor source directories and trigger backup compression and offsite transfer
  • Print queue management — Watch print directories and route documents to appropriate printers
  • EDI processing — Detect incoming EDI files and trigger parsing, validation, and routing workflows

Getting Started with Folder Monitor

Download FileWatcher and configure your first folder monitor in minutes. The visual interface walks you through directory selection, filter configuration, and action definition. Start with a single monitored folder and expand your automation as you identify additional directories to watch.

Download FileWatcher Free Trial Learn More About FileWatcher

Related Resources