Scoped To A Folder
Watch one folder and, by default, everything beneath it. A notification covers the part of your site you care about — not a firehose of everything that happens everywhere.
Get Told The Moment A File Moves
When a file is uploaded, downloaded, moved, or deleted in a folder you’re watching, Files.com sends a message about it — an email to a person, a webhook to your app, or an event into Slack, Teams, Amazon SNS, or Google Cloud Pub/Sub. No service to build, no polling loop to maintain. Files.com announces what it does into the tools your team already runs, so you react the second something happens instead of finding out later.
Stop Polling. Let Files.com Tell You.
The usual way to know when a file shows up is to write a service that asks Files.com, over and over, whether anything changed. That service needs retries when a call fails, logging when something looks wrong, and health checks to make sure it’s even running — a small system you now own and maintain, just to learn that a file arrived. It’s the wrong pattern, and it never moves the business forward.
Notifications flip it around. Files.com pushes the event to you the instant it happens — to a person by email, to your own code by webhook, or into your cloud through SNS or Pub/Sub. You stop asking Files.com what changed. It tells you.
Send Events Where Your Team Works
One event, delivered however the recipient needs it — a human in their inbox, an app at a URL, a channel, or a cloud message bus.
Email To People
Tell a person, or a whole list, when files land in a folder. Emails carry your logo, your colors, and your reply-to address, and batch up — from every five minutes to a once-a-day digest at the hour you pick — so nobody gets flooded.
Webhooks To Systems
Fire an HTTP request to your own app the instant something happens — a webhook is just a call to a URL you control. Pick GET or POST, JSON, XML, or raw, add your own headers, list a backup URL, and even ride the file’s contents along for files up to 25 MB.
Slack And Microsoft Teams
Drop a message into a Slack or Microsoft Teams channel within seconds of an event, so the people watching a feed see it where they already work, not in a console they have to go check.
Amazon SNS And Google Pub/Sub
Publish events straight into Amazon SNS or Google Cloud Pub/Sub, where your own Lambdas, queues, and pipelines pick them up. The event lands inside your cloud, ready for whatever you already have listening.
Fire Only For What Matters
Filtered By File Action
Choose which actions fire it — uploads, downloads, updates, moves, copies, deletes — in any combination. Watch only for new files, or only for deletions, or for all of it.
Narrowed By File Name
Match file names with glob patterns — only *.csv, only invoices, everything except temp files. The notification fires for the files that matter and stays quiet for the rest.
Rich Event Detail
Every message carries what happened: the action, the file path, the destination on a move or copy, an ISO-8601 timestamp, who did it, and which protocol they came in over — web, FTP, SFTP, WebDAV, or the API.
Real-Time Events Into Your Cloud
For systems rather than people, the webhook and cloud channels send one message per event, within seconds. Amazon SNS hands the event to your SQS queues, Lambdas, and HTTPS endpoints; Google Cloud Pub/Sub lands it inside Google Cloud for Cloud Functions and Dataflow. Webhooks keep retrying for about three days if a delivery fails, and email you if they keep failing, so an event your app missed during a deploy still gets through.
Notifications push events outward as they happen. If you need the retained, queryable history of everything — the kind you search months later or stream to your security tools — that’s the audit log, a separate record. See what each plan includes on the pricing page.
Notifications Questions
What teams ask about how Files.com pushes events out — which channels are real-time, how to verify a webhook, and what fires a notification.
A webhook is an automatic HTTP request Files.com sends to a URL you control the moment a file event happens. Your application receives the request and reacts — kicking off a build, updating a record, starting a downstream job — without ever polling Files.com to ask whether something changed.
Webhooks, Slack, Microsoft Teams, Amazon SNS, and Google Cloud Pub/Sub all send one message per event, within seconds. Email is the only batched channel — it groups events on an interval of at least five minutes, up to a once-daily digest at an hour you choose.
Polling means building a service that asks Files.com over and over whether anything changed, plus the retries, logging, and health monitoring to keep that service alive — work that never moves your business forward. Notifications push the event to you the moment it happens, so you skip the poller entirely.
Notifications cover activity that flows through Files.com. If a file is changed directly on an attached remote server, outside the platform, Files.com can’t see that change and won’t fire a notification for it. The events you get are every event that happens through Files.com.
Yes. Each webhook carries an x-files-signature token you can check against the request body, and Files.com publishes the IP ranges its webhooks originate from (with dedicated IPs available), so your listener can confirm a request is genuine before acting on it.
Webhook, Slack, Teams, SNS, and Pub/Sub notifications require site-admin or folder-admin rights, since they wire the platform into other systems. Email notifications are lighter — any user with History permission on a folder can set up their own.
Wire Files.com Into Your Stack
Start a free trial, point a notification at a folder, and watch every upload and delete land where your team works — an inbox, a Slack channel, or your own code — the moment it happens.
No credit card required • Free for 7 days • Live in minutes