Workflow Platforms (iPaaS)

An integration platform can coordinate application calls, transformations, approvals, and business decisions while Files.com handles the file exchange around them. These Integration Platform as a Service (iPaaS) tools connect the applications your organization already uses. Partners can submit files to Files.com without access to the receiving application; your existing workflow can collect those files, process them, and publish the resulting files for others to retrieve.

Files.com connectors expose file and folder operations and, where supported, management of share links, users, and groups. Choose the connector for the platform that already owns your application workflow. The MuleSoft, Boomi, Power Automate / Azure Logic Apps, Zapier, and Make guides explain their different operation, trigger, and error-handling choices.

Connect the File Exchange to the Application Workflow

Decide which system starts the work and which result permits the next step. Some connectors offer file triggers; others provide actions called by a schedule or another application's trigger. A Files.com Webhook can notify an external workflow of matching file activity. Trigger behavior and file-size limits differ by platform.

The connector's Files.com path can refer to native storage or a Remote Server Mount. A mounted path acts on the connected storage; it does not create a separate copy on Files.com. Choose a Sync when the job is one-way replication between supported storage locations. Use the iPaaS workflow when application processing or business decisions determine what happens to the file.

Give the Connection the Access It Needs

For a Files.com API connector, connect with a dedicated user API key whenever possible. For a workflow that only works with files and folders, use a non-administrator account and a Files Only key. The user's folder permissions, the key's path restriction, and its Workspace scope determine which locations the integration can use. Copying or moving files requires access to both paths.

Actions that manage share links, users, groups, or other resources need a Full Access key and the corresponding authority of its account. A Full Access key does not grant the user additional permissions. Use separate keys for separate integrations so retiring one connection does not interrupt another.

A platform's standard SFTP connector uses the Files.com user's SFTP authentication method and folder permissions. Use a dedicated machine account and configure the password or SSH key that connection requires. SFTP file operations do not expose the API connector's user, group, or share-link management actions.

Verify the Result Before Advancing

A successful download means the workflow received file contents; the application must separately confirm that it accepted them. With Buffered Uploads, a successful upload means Files.com received the file before delivery to the Remote Server finishes. Verify the stage that the next step depends on.

Use the platform's execution history together with Files.com API Logs or SFTP Logs, according to the connection, and the receiving application's records. Connector retries can recover individual requests, but do not establish that the entire workflow completed. Before repeating a run, determine which files were already delivered or processed and how the workflow identifies them. Delivery Verification & Failure Recovery explains how to recover without treating every step as unfinished.