Files.com publishes a real Boomi connector, not a generic SFTP step. From a Boomi Process it can work with files, folders, share links, users, and groups on your Files.com site. It retries failures on its own, so a brief network hiccup doesn't kill the Process.
Boomi moves data between applications, partners, and systems. It is not a file-transfer platform, so it has no partner protocols, no folder-by-folder access rules, and no audit trail of its own. The Files.com Partner Connector for Boomi lets a Process drive the whole Files.com site through the API.
Files.com publishes and maintains a real Boomi connector, listed as “Files.com - Partner Connector.” It is not a generic SFTP step. You build Processes against it with point-and-click Actions and Operations, so you write no glue code.
Copy, Create, Delete, Download, List, Move, Show, Update, and Upload, across files, folders, groups, share links, and user accounts. A Process can do anything the Files.com site can do, not just move files.
The connector talks to the Files.com API directly and retries failures on its own. It is faster and more dependable than the old SFTP and FTP steps. Use it on every Boomi file Process, not a raw SFTP connector, so a Process keeps running through a hiccup instead of failing on it.
Files.com handles the partner protocols, the access rules, and the record of what happened. Boomi connects the systems. File intake and secure transfer belong on Files.com, and the orchestration stays in Boomi, so you stop building file-transfer machinery inside your flows.
The connection is a single Files.com API key, stored encrypted and reusable across as many Processes as you need. Set up access once, and the key’s access scope applies everywhere it’s reused.
The Boomi connection is one Files.com API key. Make it site-wide for full access, or scope it to one user to limit which folders a Process can reach. Every action runs through the API and lands in the logs. That is the access control and audit trail Boomi doesn't give you for file work.
A site-wide key reaches every folder. A user-scoped key limits a Process to that user's folders. A Process can reach exactly the folders its key allows, and nothing more.
The API key is stored encrypted and carries nothing that identifies it on sight. Give each connection a clear name, so your integration team can tell its Processes apart.
Everything the connector does appears in the Files.com logs, so your team keeps a full record of what each Boomi Process did to the files.
A supplier sends inventory updates or purchase orders into a Files.com folder over SFTP. A scheduled Boomi Process downloads them and loads them into SAP or NetSuite. The files land on Files.com; Boomi handles the ERP side.
A Process finishes its work and uploads the result into a partner's Files.com folder. SFTP credentials or a share link make it available, with a full record of who took it.
A Process reacting to an HR system event uses the Create, Update, and Delete actions on Users and Groups to keep Files.com access in step with your directory.
A Process uses the Create and Update actions to hand out download links and set when they expire, as part of a larger fulfillment flow, so no one has to make them by hand.
Run file workflows on Files.com itself for the steps that belong there rather than in Boomi.
Learn MoreThe controlled way to hand out files. The connector can create and manage these share links from a Process.
Learn MoreEvery connector action kept in a tamper-proof, exportable record behind the Process's file work.
Learn MoreWhat buyers ask about how Files.com connects to Boomi, what it costs, and what the integration actually does.
Start a free 7-day trial, create a Connection with a Files.com API key, and run a real file operation from a live Process. No credit card required.
No credit card required • 7-day free trial • Setup in minutes