Files.com publishes an official Zapier app. A partner uploads a file over SFTP, a customer adds one, someone downloads a copy. Any of those events can start a Zap into Salesforce, Slack, Gmail, or any of the thousands of apps Zapier connects. The file itself stays on Files.com, where you control who can reach it and keep a record of everything that happens to it. Zapier was never built to do that part.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Zapier is great at moving records and firing actions across thousands of apps. What it doesn't have is a real home for the files. Files.com is that home. It speaks the protocols partners use to send files in, it decides who can see what, and it keeps a record of everything. The official Zapier app turns any file event on your Files.com site into a trigger an ops owner can build on without writing code.
Files.com publishes and maintains a real Zapier app. Connect your account with an API key and build Zaps straight against Files.com triggers and actions, so the connection is supported and stays current instead of being something you maintain.
A Zap can do more than move a file. Triggers fire on a new upload, file, folder, user, or group, and actions upload files and create folders. The same app that routes a partner feed also reacts when a user or group is created.
Use the official app on every file Zap instead of a generic SFTP connector. It calls the Files.com API directly rather than tunneling transfers over SFTP, so file steps run faster and more reliably inside the same Zap.
Replace the pile of cron jobs and scripts that shuffle files between systems with a Zap an ops owner can change without filing a ticket. The files stay on Files.com, controlled and logged. Zapier handles the apps on the other end.
A vendor's nightly feed, a customer's upload, a partner's SFTP drop: each one fires the same New File Uploaded trigger. A file coming from outside your company automates exactly like one of your own, so you write one Zap instead of a separate handler per source.
The key a Zap signs in with sets exactly what it can touch. The same access rules that decide what your people can see also decide what a Zap can see. And every action it takes is written to the logs a SOC 2 review will ask for.
A site-wide API key lets a Zap reach every folder. A user-scoped key limits it to just the folders that one user can see, so a marketing Zap can't read a finance folder.
Everything the app does lands in the Files.com logs, where your admins can see it. You get Zapier’s no-code speed and still keep a full record of what happened.
Files.com signs each webhook with an x-files-signature token and can send only from known IP addresses. So your Zapier endpoint can be sure a request really came from Files.com and not someone faking it.
A new upload, file, folder, user, or group on your Files.com site starts a Zap on its own. There's no polling script to keep alive and nothing sitting in the middle.
The Upload File action isn't limited to your Files.com folders. Dedicated actions send files on to a Remote Server, a Snapshot, or a Child Site, so a Zap can land a file exactly where the next system reads it.
A Zap isn't just for uploads. A download, a move, or a delete on a Files.com folder can start a workflow as well, so a customer pulling a file or a partner removing one each kicks off its own automation.
The official Files.com app connects with an API key and runs Zaps off real file events and actions. This is the path for most workflows, and there's nothing to keep running between the two.
Some events the built-in triggers don't cover: downloads, deletes, and moves. For those, and for busy folders, a Files.com folder webhook fires the Zap instead. No file activity slips through unautomated.
A partner uploads a file over SFTP to a Files.com folder. The New File Uploaded trigger fires a Zap that logs the activity in Salesforce and posts to a Slack channel. No polling, no script per partner.
A folder webhook fires the moment a file is read. The Zap sends a branded email through Gmail when a customer downloads from their own folder.
An upstream app passes a company name and timestamp. The Upload File action writes the file to /intake/<CompanyName>/<Timestamp>/, so incoming files sort themselves with no manual step.
Some workflows get too big for Zaps and glue: many steps, retries you can trust, changing the file as it moves. The same Files.com site can run that automation itself, so you don't have to move the files anywhere to make the jump.
Move, convert, route, and notify on a schedule or on arrival, on the same site your Zaps already watch.
Learn More
The most common place a Zap sends file alerts: a message to a channel the moment a partner drops a file.
Learn MoreEvery read, download, and permission change kept in a tamper-proof, exportable record behind the Zaps your app fires.
Learn MoreThe same API the Zapier app uses, for teams that would rather write code than build in the no-code designer.
Learn More
The same operating layer now moves campaign leads into Slate, gives remote teams a shared record of client deliveries, and anchors Carnegie’s answers to university security reviews.
“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.”
How the official Files.com app connects to your Zapier account, what it can trigger and do, and how the connection stays governed.
Files.com is an official app on Zapier. You connect your Files.com account with an API key, then build Zaps using Files.com triggers (New File Uploaded, New File or Folder Created, Group Created, User Created) and actions such as Create Folder and Upload File. No code is required.
Yes. A download, a move, or a delete on a Files.com folder can start a Zap: a Files.com folder webhook fires it through Zapier's Catch Hook trigger. The app's built-in triggers cover new uploads, files, folders, users, and groups, and the webhook covers the rest, so a customer pulling a file or a partner removing one still kicks off its own automation.
The official Files.com app is the one to use on every file Zap. It signs in with a Files.com API key and calls the Files.com API directly instead of tunneling transfers over SFTP, so it runs faster and more reliably than a generic SFTP step. It also gives you triggers and actions a raw SFTP connector doesn't have: new-file, user, and group triggers, folder creation, and uploads that name files and folders from Zap data fields.
The connection signs in with a Files.com API key. A site-wide key reaches every folder. A user-scoped key limits the Zap to just the folders that user can see. Everything the app does is written to the Files.com logs.
Yes. A partner or vendor sending a file over SFTP or FTPS into a Files.com folder fires the same New File Uploaded trigger. The Zap that logs the activity, alerts a channel, or routes the file works the same whether the upload came from your own team or from someone outside the company.
The Files.com app on Zapier replaced the older BrickFTP app. Zapier no longer allows updates or fixes for apps built on its legacy platform, so the BrickFTP app is no longer supported or updated. Rebuild those Zaps on the current Files.com app to keep receiving new triggers, actions, and fixes.
File transformation belongs on Files.com, not in the Zap. Format conversion, renaming, splitting, and encryption run natively as TransformScript and Automations on Files.com, which keeps each Zap short and holds Zapier task usage down. Keep the Zap for app-to-app actions.
Files.com delivery monitoring catches the file that never arrives. A Zap trigger can't see absence, and a feed that stops just means silence. Delivery monitoring defines when each feed is due and alerts the moment one is late.
Yes. Every file that fires a Zap stays under Files.com governance: logged in the immutable audit trail and covered by folder permissions, retention, and PGP settings. The Zap is a reaction. The governance is the platform's.
Start a 7-day free trial, connect your Files.com account with an API key, and build a Zap on a real file event. No credit card required.
No credit card required • 7-day free trial • Live in minutes