Folder Monitoring: Watch Directories for File Changes
Folder monitoring is the foundation of file-based workflow automation. By watching directories for new, modified, deleted, or renamed files, you can trigger automated processing the instant something changes. FileWatcher provides robust folder monitoring for local drives, mapped network drives, and UNC paths — detecting file events reliably and feeding them into configurable action chains.
What is Folder Monitoring?
Folder monitoring is the process of continuously observing one or more directories for file system changes. When a monitored folder receives a new file, or an existing file is modified, renamed, or deleted, the monitoring system detects the event and can trigger downstream actions. This is the fundamental capability that enables all file-based automation — without reliable detection, no automated workflow can begin.
In enterprise environments, folder monitoring replaces manual checking routines where staff periodically look at directories for new arrivals. Instead of a person opening Windows Explorer every few minutes, FileWatcher continuously monitors your target folders and responds to changes within seconds. This eliminates delays, ensures nothing is missed during off-hours, and frees staff for higher-value work.
Types of File Events to Monitor
A comprehensive folder monitoring solution must detect multiple types of file system events. Each event type serves different automation scenarios:
New File Detection
The most common monitoring scenario is detecting when new files appear in a directory. This triggers processing workflows for incoming data feeds, uploaded documents, generated reports, or files dropped by other systems. FileWatcher detects new files the moment they are fully written and closed, avoiding the common problem of processing incomplete files that are still being transferred.
File Modification Events
Detecting when existing files are modified enables workflows that respond to updates. Configuration files that control application behaviour, data files that receive appended records, or documents that undergo revision can all trigger automated responses when their content changes. FileWatcher tracks file modification timestamps and sizes to identify genuine changes versus filesystem metadata updates.
File Deletion Monitoring
Monitoring for deleted files supports compliance and housekeeping workflows. When regulated files are removed unexpectedly, deletion monitoring can trigger alerts or logging. It also enables workflows where removing a file signals completion of a processing stage — the downstream step watches for the file to disappear before proceeding.
File Rename Detection
Rename events are important in workflows that use filename conventions to signal status. A common pattern is renaming files from a temporary extension (like .tmp or .partial) to a final extension (like .csv or .xml) once writing is complete. FileWatcher detects these renames and can trigger processing based on the new filename matching configured filters.
Monitoring Local Drives and Network Paths
Real-world automation requires monitoring files wherever they reside. FileWatcher supports multiple path types to cover all deployment scenarios:
Local Drive Monitoring
Monitoring local drives (C:\, D:\, etc.) provides the fastest and most reliable event detection. File system notifications from the operating system arrive instantly, and there are no network latency or connectivity concerns. Use local monitoring for processing pipelines where source files are written directly to the server running FileWatcher.
Mapped Network Drives
FileWatcher monitors mapped network drives (Z:\SharedData\Incoming, etc.) for environments where files arrive on network-attached storage or file servers. Because mapped drives depend on the user session, FileWatcher's Windows Service mode uses stored credentials to maintain access regardless of whether a user is logged in.
UNC Path Monitoring
For enterprise deployments, UNC paths (\\server\share\folder) provide direct network access without drive letter dependencies. FileWatcher connects to UNC paths with configurable credentials, making it ideal for monitoring shared folders across departments or locations. UNC monitoring works reliably even when no user is interactively logged into the machine.
Configuring Polling Intervals
Folder monitoring relies on polling — periodically scanning the target directory for changes. The polling interval determines how quickly changes are detected and represents a balance between responsiveness and resource usage:
- Short intervals (1-5 seconds) — Near-instant detection for time-critical workflows. Use when processing delays of more than a few seconds are unacceptable, such as real-time data ingestion or urgent document routing
- Medium intervals (10-30 seconds) — Suitable for most business automation. Files are detected quickly without generating excessive disk I/O on the monitoring system
- Long intervals (1-5 minutes) — Appropriate for batch-oriented workflows where immediate detection is not required. Minimises resource usage when monitoring high-traffic directories or remote network paths with latency
FileWatcher lets you configure polling intervals per monitored folder, so time-critical paths can use aggressive polling while less urgent locations use longer intervals. This balances responsiveness with system resource efficiency across your entire monitoring configuration.
File Filters and Pattern Matching
Most monitored folders contain a mix of file types, but your workflow typically cares about specific files. File filters let you narrow monitoring to relevant files:
- Wildcard patterns — Match files by extension (*.csv, *.xml) or naming convention (INVOICE_*.pdf, RPT_????????.txt)
- Inclusion filters — Only trigger on files matching specified patterns, ignoring everything else
- Exclusion filters — Trigger on all files except those matching exclusion patterns (useful for ignoring temporary or system files)
- Size filters — Only process files above or below a specified size threshold, filtering out empty placeholder files or oversized anomalies
- Age filters — Require files to remain unchanged for a configurable period before triggering, ensuring large file transfers complete before processing begins
FileWatcher combines these filter types to create precise targeting rules. For example, you might monitor for *.xml files larger than 1KB that have remained unchanged for at least 10 seconds — ensuring you only process complete, valid XML deliveries.
Handling File Stability
A critical challenge in folder monitoring is distinguishing between a file that has finished arriving and one that is still being written. Processing an incomplete file produces errors, corrupted output, or missing data. FileWatcher addresses this with stability checking:
- File lock detection — Attempts to open the file exclusively before triggering. If another process holds the file open for writing, FileWatcher waits and retries
- Size stability — Monitors file size over successive polling cycles. Processing only triggers when the file size stops growing
- Age threshold — Requires the file's last-modified timestamp to be at least N seconds in the past before triggering
These mechanisms work together to ensure your automated workflows always process complete files, even when dealing with slow network transfers or applications that write data incrementally.
Subdirectory Monitoring
Business file structures often use subdirectories to organise data by date, department, customer, or file type. FileWatcher supports recursive monitoring that watches an entire directory tree, detecting changes at any depth. You can configure whether subdirectory monitoring includes newly created subdirectories automatically, ensuring your monitoring adapts as folder structures evolve.
Monitoring Best Practices
Effective folder monitoring requires thoughtful configuration. Follow these guidelines to build reliable monitoring setups:
- Monitor dedicated folders — Create specific input folders for automation rather than monitoring general-purpose directories. This reduces noise and simplifies file filters
- Use stability checks — Always configure file stability verification to prevent processing of incomplete transfers
- Handle network interruptions — For network path monitoring, configure FileWatcher's reconnection settings to automatically recover from temporary network outages
- Log all events — Enable comprehensive logging to track what was detected, when, and what action was triggered. This is invaluable for troubleshooting and audit trails
- Test with realistic volumes — Verify your polling interval and filter configuration handles peak file arrival rates without missing events or creating backlogs
- Separate concerns — Use different monitoring tasks for different workflow types rather than combining unrelated processing in a single monitor
Integration with Processing Pipelines
Folder monitoring is only the first step. Once FileWatcher detects a file event, it feeds into automated file processing pipelines that handle the file end-to-end. Common integrations include passing files to TextPipe for data transformation, uploading via FTP automation, or feeding into triggered batch processing workflows.
For complex business workflows, folder monitoring provides the event-driven trigger that starts multi-step processing chains. FileWatcher's action chaining means a single file detection can initiate a sequence of operations — validate, transform, route, archive, and notify — all without manual intervention.
Get Started with Folder Monitoring
FileWatcher makes folder monitoring simple to configure and reliable to operate. Set up your first monitored folder in minutes through the visual interface, then build out your automation workflows step by step. Whether you are monitoring a single input folder or coordinating dozens of directories across a network, FileWatcher scales to your requirements. See also our guides on file watcher Windows for a complete overview of triggers, actions, and service mode, and our step-by-step folder monitor configuration guide.