MuleSoft is built to move records between applications. Files.com is built to move files between organizations — partner SFTP, PGP encryption, and the audit trail that comes with them. An official connector on Anypoint Exchange joins the two, and jobs that are only file work can run on Files.com with no flow to build at all.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
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, gives a Mule flow the Files.com API as drag-and-drop operations: files, folders, share links, users, and groups. 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; and manage share links, users, and groups. The same flow that moves the file can hand out the share link and manage who has access, all from one connector.
The connector talks to the Files.com API directly, so 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. And a job that is only file work (pick up, decrypt, reshape, deliver) runs entirely as Files.com Automations, no flow required.
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.
Built on the official Files.com Java SDK, the connector retries a failed operation up to three times on its own. 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 webhooks fire the moment a file lands, so a Mule flow's HTTP listener starts processing right away instead of waiting for the next poll. Partner files stop sitting in a folder until a schedule notices them.
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 More
The shift had to satisfy an Azure hosting constraint while handling partially written files, partner endpoints, and growing system-to-system traffic without custom code.
Read The Story
Oracle Fusion went directly to Files.com while legacy teams migrated business-critical file jobs at their own pace.
Read The Story
The team staged the cutover before its seasonal freeze, with Files.com handling API transfers, alerts, and code-free archiving behind the existing partner interface.
Read The Story
Files.com gave the shared-services team strict identity and data-isolation controls for each maison while letting new integrations build on a platform the group had already assessed.
Read The Story
“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 Files.com connector fits into your Mule flows, which plan includes it, and which file jobs don't need a flow at all.
Yes. The Files.com Connector for MuleSoft is published on the MuleSoft Anypoint Exchange. Install it in Anypoint Studio and drag its operations into your Mule flow. It is the recommended way to integrate with Files.com from MuleSoft.
The Files.com connector moves files faster and holds up better than the generic SFTP and HTTP steps, and it manages share links, users, and groups as well as files and folders. Use it on every Mule file flow rather than a raw SFTP connector.
Yes. The Files.com connector retries network and service failures on its own, so a brief hiccup doesn't kill the flow the way a generic SFTP step would. If a failure won't clear, it surfaces to the Mule flow so you can handle it your own way.
The Files.com connector signs in with an API key. An admin can hand out a key scoped to one user to limit folder access, or a site-wide key for full access. Every connector operation is written to the Files.com logs.
The official Files.com Connector for MuleSoft is available on the Power plan and above. Every plan includes the REST API, SDKs, and CLI, so a Starter site can still be driven from a Mule flow in code. The drag-and-drop connector unlocks at Power. See what each plan includes on the pricing page.
Yes. Files.com TransformScript reads just like DataWeave, and most DataWeave-style scripts run as-is, so a MuleSoft shop can move the transforms that belong at the point of file intake straight onto Files.com. You can connect from Anypoint Studio and run transforms on Files.com. Both work.
Files.com doesn't replace MuleSoft for API integration. MuleSoft connects your systems of record, and a Mule flow plugs into Files.com for its file work. Many file-only jobs do move off Mule entirely: a pickup-transform-deliver pipeline with EDI, AS2, and PGP runs as Files.com Automations with no flow to build or maintain.
Yes. Files.com webhooks fire on upload events, so a flow's HTTP listener starts processing the moment a counterparty's file lands instead of on the next poll.
Run record-level mapping between systems in DataWeave, and file-shaped work on Files.com. TransformScript and Automations handle format conversion, splitting, renaming, and per-recipient encryption at the file layer, rather than as flow logic.
Yes. Partners on plain FTP, mandated AS2 with signed receipts, or browser-only workflows deliver into governed Files.com folders, and the flow reads one consistent landing zone regardless of how each file arrived.
Start a 7-day free trial, install the connector from the Anypoint Exchange, and run a real file operation from a live flow.
No credit card required • 7-day free trial • Live in minutes