Boomi

Boomi lets you connect Files.com to thousands of other applications, systems, processes, and workflows. Boomi provides a visual, point and click interface for building integrations through a browser-based UI. Processes and integrations can be set up quickly, with no coding, to automate your business tasks and workflows.

Getting Started with Boomi

• Log in to your Boomi account or create a new Boomi account.
• Navigate to "Services" then "Integration".
• Select "Create New" then "Connection" and choose "Files.com - Partner Connector" from the list.
• Use your Files.com API Key to connect your Files.com account to Boomi. (Create a site-wide API Key for full access to all folders on your site without requiring a user account, or create an API Key for a specific user if you want to restrict access to certain folders. Please refer to our documentation for creating API keys.)

Once that's done you can start creating Boomi Processes to automate the transfer of data between your Boomi process and your Files.com account.

Documentation for the Files.com Partner Connector can be found on the Boomi Help site.

Files.com Partner Connector Configuration

The Files.com connector shape requires a Connection, an Action, and an Operation to be specified for its use.

Connection

The Connection defines the Files.com account which will perform the actions. It requires a Files.com API Key to authenticate and authorize the actions. Connections can be re-used in as many connector shapes as needed.

Ask your Files.com administrator to provide you with an API Key for the required user account or generate your own API Key within your Files.com user account. The connection uses a single Files.com API Key.

When creating a new connection: within the Connection tab, select the Click to Set button, enter the API Key, and select Apply.

Make sure to name the connection clearly, or provide a description, as the API Key does not show any identifying information and will be stored in an encrypted state.

Connector Actions

The Action defines the action to be performed on Files.com by the connector shape. Available actions are List folder items, Download a file and Upload a file.

• The List folder items action is used to list the items contained within a Files.com folder and its results can be used to further traverse the Files.com folder structure, to determine a file to download, or to determine a target folder location for a file upload.
• The Download a file action is used to download a file’s contents from Files.com into your Boomi process. You can specify the file name and folder path for the download.
• The Upload a file action is used to upload data from your Boomi process, as a file, into a Files.com folder location. You can specify the file name and folder path for the upload.

Connector Operations

The Operation defines a specific configuration for the chosen action, allowing you to specify folder paths and file names for the operation. You can define as many operations as required. Operations can be re-used in as many connector shapes as needed.

Refer to the Boomi Help documentation for details about configuring Connector Operations.

Troubleshooting the Boomi Files.com Partner Connector

The Files.com Partner Connector shape could fail or have issues due to the following causes.

Invalid API Key

Verify the response document of the Files.com shape in your Boomi process.

API Keys that are invalid or revoked will return a response document containing the following error message:

{
  "error": "The API key or Session token provided could not be used to validate this request. Internal Error Code: API1",
  "http-code": 401,
  "instance": "0434fde9-1967-4019-a4db-02ddc2001a1e",
  "title": "Invalid Credentials",
  "type": "not-authenticated/invalid-credentials"
}

Update the connector with a valid API Key and re-try the process.

Incorrect API Key Permissions

If your API Key does not have permission to access an item on Files.com, the response document will contain the following error:

{
  "error": "Not Found",
  "http-code": 404,
  "instance": "fa8f115b-0ffd-4abd-a37e-dc91a4518c06",
  "title": "Not Found",
  "type": "not-found"
}

Make sure that the API Key you are using has permission to access the item on Files.com or update the API Key to a new one that has permission to access the item.

Trying to use List Folder Items on a non-existent folder

If you try to list the contents of a non-existent folder, the response document will contain the following error:

{
  "error": "Not Found",
  "http-code": 404,
  "instance": "fa8f115b-0ffd-4abd-a37e-dc91a4518c06",
  "title": "Not Found",
  "type": "not-found"
}

Make sure that the folder that you are trying to List on Files.com exists. You can observe and traverse the available folder structure by starting your List Folder Items operation at /, the root folder.

Trying to use Download A File on a non-existent file

If you try to download a non-existent folder, the response document will contain the following error:

{
  "error": "Not Found",
  "http-code": 404,
  "instance": "fa8f115b-0ffd-4abd-a37e-dc91a4518c06",
  "title": "Not Found",
  "type": "not-found"
}

Make sure that the file that you are trying to download exists by using the List Folder Item action, on the folder containing the file, prior to attempting the download.

Trying to upload a file into a non-existent folder

If the target folder does not exist, the Connector will create the entire folder path for you so that the file uploads successfully.

Trying to upload a file into a folder which your API Key has no access permissions for

If the target folder cannot be accessed, because the API Key has incorrect permissions, then the upload will fail and the response document will contain the following error:

{
  "error": "Not Found",
  "http-code": 404,
  "instance": "fa8f115b-0ffd-4abd-a37e-dc91a4518c06",
  "title": "Not Found",
  "type": "not-found"
}

Make sure that the Folder that you are trying to upload to is accessible by the API Key, prior to attempting the download. If the API Key type is site-wide then this error shouldn't occur as site-wide API Keys have access to all folders. If the API Key is owned by a user account then make sure the user account has access permissions to the target folder.