When a file lands in a folder you're watching, Files.com publishes a tidy message to your Pub/Sub Topic, or one a partner or another team owns. Pub/Sub sends it to every Cloud Function, Cloud Run service, Dataflow job, and subscriber. So there's no function sitting there watching a bucket to build or babysit.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Pub/Sub is great at one thing: publish a message to a Topic once, and it reaches every subscriber. What Pub/Sub doesn’t do is the file part. That means taking files in from partners over SFTP and FTPS, controlling who can touch which folder, and keeping an audit trail. Files.com does that part, and publishes a message to your Topic the moment a file lands. Your existing fan-out takes it from there.
When something happens in a folder you're watching, Files.com publishes a message to your Pub/Sub Topic. Pub/Sub delivers it to everything subscribed, so the work fans out the moment the file arrives and nothing has to poll for it.
The message says what happened, where, by whom, from what address, over which protocol, and the file's name, type, and size. That's enough for a Cloud Function or Dataflow consumer to route and process the file without opening it first.
Today you run a Cloud Function that listens for GCS bucket events just to find out a partner's file showed up. Let Files.com be the front door instead. It takes the file in and publishes the event itself, with the access controls and audit trail a raw bucket path doesn't give you.
Files can arrive over SFTP, FTPS, FTP, AS2, the API, an Inbox, or a Share Link. Any of those can fire the Pub/Sub event. So a partner who can only do SFTP still kicks off your Google Cloud pipeline.
The Topic can belong to another team, a vendor, or a partner running the downstream pipeline. They grant publish access on their Topic, you add the credential, and your files start feeding their pipeline without either side building a bridge.
Files.com publishes with a Google Cloud service account that can do one thing: put a message on the Topic, and nothing else. Setting up the event stream never widens what an attacker could reach in your Google Cloud project.
The event fires when a file lands over any path in, whether or not the storage behind the folder is Google Cloud Storage. SFTP, FTPS, FTP, AS2, the API, an Inbox, or a Share Link all work.
Files.com publishes one message per file operation, the instant it happens. No waiting, no lumping things together. A Cloud Function or Dataflow consumer reacts the moment a file lands.
Files.com records every event in its own audit log, separate from Pub/Sub. So the Pub/Sub stream is never your only record. The full trail is still there even if a subscriber misses a message.
A partner uploads a file over SFTP, Files.com publishes the event to Pub/Sub, a Cloud Function picks it up and processes the file, and a Dataflow job loads it. Nobody touches it in between.
Every data feed that lands in Files.com fires a Pub/Sub event that kicks off a Dataflow job or a BigQuery load. Your analytics stay current instead of waiting on a job that runs on a timer.
One folder's activity publishes to a Topic that several Cloud Run services listen to on their own. One pulls metadata, one processes the document, one archives it, each reacting independently.
The who, where, and from-what-address details feed a subscriber that writes to your SIEM, turning file activity into security data your team can watch.
Your storage behind it all. Pointing Files.com at a GCS bucket and publishing Pub/Sub events is the classic Google Cloud setup.
Learn MoreRun file jobs inside Files.com instead of stitching together Cloud Functions and schedulers.
Learn MoreThe same idea over plain HTTP, for when the thing receiving the event isn't on Google Cloud.
Learn MoreThe full, separate record of activity that sits behind the Pub/Sub stream.
Learn MoreApril 13–15, 2027 · Las Vegas, NV
Files.com builds deeply on Google Cloud Storage, Drive, and Workspace, so of course we’ll be on the floor at Google Cloud Next telling our File Orchestration story. The legacy MFT vendors won’t be there.
See Files.com At Google Cloud Next
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
Before you point a folder at a Pub/Sub Topic: how Files.com publishes, what each message carries, and what happens when a subscriber misses one.
Files.com publishes a message to your Pub/Sub Topic each time matching activity happens in a folder you're watching, using a Google Cloud service-account credential you provide. From there Pub/Sub delivers the message to every subscriber on the Topic: Cloud Functions, Cloud Run, Dataflow, BigQuery, or any push or pull endpoint.
The message says it came from Files.com and includes what happened, where, by whom, from what address, over which protocol, when, and the file’s name, type, and size, with both paths for copies and moves. That’s enough for a subscriber to route and process the event without opening the file. It’s the same message Files.com publishes to Amazon SNS.
Yes. Files.com publishes with whatever service-account credential you configure, so the Topic can belong to another team, a vendor, or a partner who runs the downstream pipeline. They grant publish access on their Topic, and you add that credential to the notification.
By default, Files.com publishes a message for any upload, download, change, delete, move, or copy in the folder you set and its subfolders. You can narrow which actions fire and whether subfolders count.
No. Files.com fires the Pub/Sub event when a file lands over any path in, whether or not the storage behind it is Google Cloud Storage. SFTP, FTPS, FTP, AS2, the API, an Inbox, or a Share Link all work.
No. Files.com publishes one message per file operation, the instant it happens, without lumping several operations into a single message.
Files.com records every event in its own immutable audit log, separate from the Pub/Sub stream, so a missed message never means a missing record.
Yes. That is the classic pipeline: a file lands, Files.com publishes the event, and a subscribed Dataflow job or Cloud Run service loads the data into BigQuery immediately instead of waiting on a timer.
Yes. Files.com Event Channels deliver operational events such as SSO failures, user lockouts, and automation failures to a Pub/Sub Topic as they occur, alongside the file-activity notifications.
Start a 7-day free trial. Point a folder at a Pub/Sub Topic, run a test upload, and watch the event reach your subscribers. No credit card required.
No credit card required • 7-day free trial • Live in minutes