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.
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. It is not the generic SFTP step you would otherwise wire up by hand. 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.
The app talks to the full Files.com API, so a Zap can do far more than move a file. Triggers fire on a new upload, file, folder, user, or group; actions create folders and upload files.
The Files.com app is built for the job, so it signs in and runs reliably. Use it on every file Zap. Don't bolt a generic SFTP connector onto the workflow. The official app handles the retries a raw SFTP step won't, so a file doesn't go missing when a transfer hiccups.
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 thousands of 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.
A Zap can file an incoming upload by the details that came with it, so files land in folders like /intake/<CompanyName>/<Timestamp>/ on their own, instead of waiting for someone to sort them by hand.
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, so 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.
Run file workflows on Files.com itself when a Zap gets too big: many steps, retries you can trust, and scheduling.
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 MoreWhat buyers ask about how Files.com connects to Zapier, what it costs, and what the integration actually does.
Start a free 7-day 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 • Setup in minutes