MuleSoft
Use the Files.com connector in an existing Mule flow when files are the input or output of application processing. A download operation brings file contents into the flow for transformation or another application's connector; an upload publishes the flow's output to a Files.com path. Mule owns the sequence and application logic. Files.com provides the file locations and access used by people, partners, and systems.
The Files.com Connector for MuleSoft is available on the MuleSoft Anypoint Exchange. We recommend it over a generic SFTP or HTTP connector: it uses the Files.com APIs and SDK, including their file-transfer and error-handling support, and exposes operations beyond file transfer.
Getting Started with MuleSoft Anypoint
Use Anypoint Studio to install the Files.com MuleSoft Connector from the Anypoint Exchange.
Drag and drop any of the connector's operations into your process flow to begin using them.
Authentication
The connector requires a Files.com API Key to authenticate and authorize the actions.
Use a dedicated non-administrator user and a Files Only key for flows that only work with files and folders. Give that user the required folder permissions, and choose the key's path and Workspace scope for the flow. Operations that manage share links, users, or groups require a Full Access key and the appropriate account permissions.
Connector Operations
Available connector operations include:
- Files - Upload, download, copy, move, and delete files.
- Folders - Create, list, copy, move, and delete folders.
- Share Links - Create, list, update, and delete secure share links to files and folders.
- Users - Create, list, update, and delete user accounts.
- Groups - Create, list, update, and delete groups.
Automatic Retry Handling
The MuleSoft connector uses the official Files.com Java SDK to retry requests affected by temporary network or service conditions. These retries occur within the connector; configure the Mule flow's error handling for a failure that remains after those attempts.
Request retries do not restart the entire flow or confirm that a later application step succeeded. Before repeating a flow that uploaded, copied, or moved a file, check which operations already completed. The shared iPaaS guidance explains the distinction between request completion, onward file delivery, and application acceptance.
Troubleshooting the Files.com Connector for MuleSoft
The connector uses the Files.com APIs to perform authentication and its operations. Refer to error documentation to determine the cause of the error.
Your site administrators can also access the site's API logs to see the results of the actions that the MuleSoft connector performed.
When the Mule runtime is on-premise or in a private cloud, its network must allow the connector's API and file-transfer destinations; follow the networking requirements. For a failure accessing a Remote Server Mount, also inspect the connection to the remote system and applicable outbound-connection records. A successful API connection from Mule does not prove that the remote file operation succeeded.