Files.com publishes a real Mule connector, not a generic SFTP step. From inside a Mule flow it works with files, folders, share links, users, and groups on your Files.com site. It retries failures on its own, and it runs transforms in a script that reads just like DataWeave.
MuleSoft is built to connect APIs and records. It was never meant to be the place partners send files over SFTP and FTPS, with the access rules and audit trail that come with that. The Files.com Connector for MuleSoft, published on the Anypoint Exchange, lets a Mule flow read, write, and manage the whole Files.com site through the API. You stop bolting a generic SFTP step onto a file-transfer job it was never going to handle well.
Files.com publishes and maintains a real Mule connector, not a generic "we support SFTP" step. Install it in Anypoint Studio and drag its operations straight into a flow, so you build the integration in minutes instead of hand-wiring file steps.
Upload, download, copy, move, and delete files; create, list, copy, move, and delete folders; manage share links, users, and groups. A Mule flow can do anything the Files.com site can do, not just move a file around.
The connector talks to the API directly and retries failures on its own, built on the official Files.com Java SDK. It moves files faster and holds up better than Mule's generic SFTP and HTTP steps. Use it on every Mule file flow, so a flaky transfer doesn't page you at 2 a.m.
Files.com TransformScript reads just like DataWeave, the language MuleSoft made popular. Most DataWeave-style scripts run as-is, so your team keeps the skills it already has. A MuleSoft shop can connect from Anypoint Studio and also move the transforms that belong at the point of file intake straight onto Files.com.
Files.com handles the partner protocols, the access rules, and the record of what happened. MuleSoft handles the integration into your systems of record downstream. Each one does the part it was built for.
The connector signs in with a Files.com API key, scoped to one user or to the whole site, so the same access rules that apply to your people apply to the flow. Every operation runs through the API and lands in the logs. That is the access control and audit trail MuleSoft doesn't give you for file work.
An admin hands out a user-scoped key to limit a flow to certain folders, or a site-wide key for full access. A flow can reach exactly the folders its key allows, and nothing more, so a misconfigured flow can't touch files it was never meant to.
Everything the connector does is written to the Files.com logs, so your integration team keeps a full record of what each Mule flow did to the files.
When a flow runs from a Mule runtime in your own data center, the connector reaches Files.com over HTTPS like any normal outbound connection. There are no special inbound firewall rules to open, so you skip the security review that opening a port would set off.
The connector retries a failed operation on its own, built on the official Files.com Java SDK. A brief network hiccup won't kill the flow the way it would with Mule's generic SFTP and HTTP steps, so the run finishes instead of failing on a glitch you have to restart by hand.
Files.com TransformScript reads just like DataWeave, the language MuleSoft made popular, so most DataWeave-style scripts run as-is. A Mule shop keeps writing the file-intake transforms it already knows.
A trading partner sends a file over SFTP into a Files.com folder. A scheduled Mule flow downloads it, then runs the integration into SAP or NetSuite. The file lands on Files.com; MuleSoft handles the rest.
A Mule flow finishes its work and uploads the output into a partner's Files.com folder, where a share link or SFTP login makes it available. Files.com handles the secure delivery.
A Mule flow reacting to a Workday or Salesforce event uses the Users and Groups operations to add or remove Files.com access in step with your directory.
A team that knows DataWeave moves the work of cleaning up partner file formats onto Files.com TransformScript, right where the files come in. That frees the Mule flow to focus on connecting the systems downstream.
TransformScript that reads like DataWeave, for the file cleanup a MuleSoft shop already knows how to write.
Learn MoreThe API the connector uses and the Java SDK underneath it, for teams that want to work in code.
Learn MoreEvery connector operation kept in a tamper-proof, exportable record behind the Mule flow's file work.
Learn MoreWhat buyers ask about how Files.com connects to MuleSoft, what it costs, and what the integration actually does.
Start a free 7-day trial, install the connector from the Anypoint Exchange, and run a real file operation from a live flow. No credit card required.
No credit card required • 7-day free trial • Setup in minutes