Automated FilesAnywhere New File Alerts
Every hour, WebRun opens FilesAnywhere, checks shared folders for new files, saves a backup reference copy to Google Drive while FilesAnywhere stays the source of record, and pings the reviewer assigned to that folder in Slack.
How do I get notified when a new file lands in a shared FilesAnywhere folder?
WebRun checks FilesAnywhere every hour for new files landing in shared folders, and saves a backup reference copy to Google Drive while FilesAnywhere stays the source of record. It pings the reviewer assigned to that folder in Slack, so a new file gets a same-hour human review instead of sitting unnoticed.
- New files get a same-hour handoff to the right reviewer
- FilesAnywhere stays the single source of record
- No duplicate pings for a file already handled
Built for Business teams sharing project files · IT admins · teams using FilesAnywhere for client work
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.filesanywhere.comin a real browser with your saved login - no setup, no API keys. -
1
FilesAnywhere - check shared folders for new files
filesanywhere.com
WebRun opens FilesAnywhere to check shared folders for new files. - Open FilesAnywhere and check shared folders for new files
- Note which folder, file name, and who uploaded it
- Skip files already handled in a previous run
Done when Every new file this run is captured with its folder and uploader.
-
2
Google Drive - archive a backup reference
drive.google.com
WebRun opens Google Drive to archive a backup reference. - Save a backup reference copy of each new file
- File it under the matching project folder
- Keep FilesAnywhere as the source of record. This is a backup only
Done when A backup reference exists for every new file.
-
3
Slack - ping the assigned reviewer
slack.com
WebRun opens Slack to ping the assigned reviewer. - Post a ping to the assigned reviewer for that folder
- Name the file and where it landed
- Keep it short: enough to know something needs review
Done when The assigned reviewer has been pinged about the new file.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it remove the file from FilesAnywhere after backing it up?
No. FilesAnywhere stays the source of record. Google Drive only gets a backup reference copy alongside it.
Who gets pinged about a new file?
Only the internal reviewer assigned to that folder. No external party is contacted by this automation.
What if the same file appears twice?
It is skipped if already handled in a previous run, so nobody gets pinged twice about the same upload.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.