Troubleshooting the Boomi Files.com Partner Connector

If your process stops on an application error or passes an error response to a later step, check the operation's Return Application Error Responses setting. Confirm that the process uses a connector version that supports the setting.

Inspect the returned error response or Process Reporting to identify the failure before changing credentials or file paths. For a List action, confirm that the operation succeeded before treating a result with no items as an empty folder.

Invalid API Key

Invalid or revoked API Keys produce the following error:

[401] The API key or Session token provided could not be used to validate this request.

Update the connector with a valid API Key and retry the process.

Not Found

When the file or folder path does not exist on Files.com, or the API Key does not have permission to access it, the operation produces the following error:

[404] Not Found.  This may be related to your permissions.

Files.com returns this error for both causes.

Confirm the exact path and Workspace used by the operation. If the connection has List permission, list the parent folder to check the name; otherwise, ask an administrator to verify the path and use Check Access for the connected user. A failed listing alone does not prove that an account lacks permission to upload.

Check both the user's permission for the failed operation and the API key's path and Workspace scope. Correct the path or the required grant within the intended scope. Switching to a broadly privileged key can hide an access problem without correcting the production connection.