The Problem: Files Arrive, Nothing Happens
In most Windows environments, files land in folders — incoming invoices, EDI files, scanned documents, reports from machines — and someone has to manually check for them, process them, and move them along. Even when that job is automated, it usually means a PowerShell script running on a timer, polling every few minutes, burning CPU and missing files that arrive between runs.
There's a better way.
How Windows Folder Monitoring Works
Windows exposes a native API called the FileSystemWatcher that fires events the instant a file is created, modified, deleted, or renamed inside a directory. Unlike polling, it's event-driven: zero CPU when nothing is happening, and near-instant response — typically under 50ms — when something does.
The challenge is building reliable automation on top of it. A raw FileSystemWatcher fires duplicate events, misses files that are still being written, and gives no built-in way to call a webhook, send an email, or transfer a file.
What You Can Do When a File Arrives
Once you have reliable folder monitoring in place, you can trigger almost any downstream action:
All of this can happen within milliseconds of the file landing — no polling, no cron jobs, no manual checks.
Setting Up Folder Monitoring Without Writing Code
ForgeDrop is a Windows desktop application built on the native FileSystemWatcher API. You configure folders and rules through a GUI — no scripting required for most workflows.
Here's the basic setup:
1. Add a folder to watch
Point ForgeDrop at any local or network-mounted directory. It registers a native OS watcher immediately. For UNC paths (\\server\share) it automatically switches to polling mode to handle network latency.
2. Define a rule
Choose which event fires the rule: file added, file changed, or file deleted. Filter by file name pattern — *.pdf, report-*.xlsx, invoice_* — so only the right files trigger the rule.
3. Add an action
Pick what happens: send an email, fire a webhook, run a script, transfer via SFTP, post to Slack. You can chain multiple actions on a single rule, and add conditions so the rule only fires on files above a certain size or within a certain age.
Advanced: File Stabilisation
One common problem with folder watching is that large files trigger events while they're still being written. ForgeDrop has a settle time setting that debounces the event — it waits until the file hasn't changed for a configurable number of milliseconds before firing the rule. This prevents partial-file processing on slow network shares or large uploads.
Monitoring Subfolders
ForgeDrop supports recursive subfolder monitoring with a configurable depth limit. Watch an entire directory tree, or limit to immediate subdirectories only. It will warn you if two folders overlap so you don't process files twice.
Running as a Windows Service
For production environments, ForgeDrop's server component can be installed as a Windows Service using NSSM. It starts automatically at boot, logs to rotating log files, and runs headlessly — no user session required.
Try It Free
ForgeDrop is free to start — two folders, three rules per folder, all action types included. No credit card required.