Our Box connector allows you to use your Box.com account for both External Post Production and Asset delivery. So you can harness their scaleable and secure storage with your post-production providers and as a final resting place for your assets once they are done in Creative Force.

Setting up the Integration in Box.com

Box uses JSON Web Tokens (JWT) as the most common way of connecting to External applications like Creative Force. Further information can be found on their knowledge base article on the topic.

The JWT flow

As a first step, you will want to ensure that you have two-factor authentication turned on for your Box account, via your Account settings as shown below:


From there, you will want to navigate to the Dev Console.


Once you are in the Dev Console, you will need to create a new app, by selecting "Custom App" from the options as shown below:


Then you can select Server Authentication (with JWT) and choose the name of the application and then create the app.

Note: You will need to have different Custom apps for External Post and Asset Delivery. Similarly, if you have multiple Asset Delivery locations or External Post Production Providers within your Box account, you will want to have custom apps for each.

When the app has been created, you will want to then navigate to the Application Scope section, and then allow for the following settings:

  • Read all files and folders stored in Box

  • Write all files and folders stored in Box

  • Manage webhooks

Note: If you change these settings in the future, you will have to reauthorise the app.


After defining the application scope, you can then move to the Add and Manage Public Keys so that you can generate a Public/Private Keypair. You will want to save the config.json file for use later during the step-up steps in Gamma.

Note: This step requires Two-factor Authentication to be enabled.

The first time you click on Generate a Public/Private Keypair you will be asked for a two-factor authentication step. Once done, it will redirect you back to the app page where you can click on the button again, and the JSON file will be downloaded.


When you have created the JSON file via the Generate a Public/Private Keypair button and saved the file in a safe place, you can then move over to the Webhooks section.

Once there, you will want to generate a Primary, and Secondary Key. Make sure to save these as well, for use in Gamma in just a moment.


Afterwards, navigate to the Authorisation section and click on Review and Submit


After this is done, you will need to go to the Admin section to enable the app.


Once in the Admin Section, navigate to the Apps section and, Custom Apps. From there, you can Authorise the app.


For External Post Production Set Up Only

If you are using the Integration for External Post, you will also have the following steps to complete.

After the app has been authorised by an Admin, you will want to go to the Content Section in the Admin Panel, and right-click on the newly created app and click on Log in to user's account. This will allow you to impersonate the app and create the Upload and Download folder in Box for your post-production vendors.


Once you are have started to impersonate the App, you will want to create a Download folder, and Upload folder for your External Vendor to send and receive images from Creative Force.


From there you are ready to set up the integration in Creative Force!

Setting Up the Box.com Integration in Gamma for External Post

When you have done the above steps, you will want to go Gamma (The Creative Force Web App) and navigate to Studio Setting, and Post Production.

From there you can click on Add and choosing Box.com as the Connection Type.

When you click next you will see a list of options to populate as below. You will want to open the JSON file via your Browser and paste the values from the file into the corresponding sections within Creative Force.


Once you have entered all of the information, you can then hit Test. Once that is successful, you can then specify the Upload and Download folders as previously mentioned.


When the folders are set up, you can test them again. Once it is successful, it will appear as below:


Afterwards, you can then start using the connector with your post-production vendor!


Setting Up the Box.com Integration in Gamma for Asset Delivery

If you want to use the Box.com integration for asset delivery, you can follow the below steps to get it set up.

Note: You will need to complete part one in your Box account before completing these steps.

You will want to navigate to the specific client that you want to add the asset delivery location. First, editing the client then navigating to Delivery Options where you can add the Box.com integration.

Once you have selected Box.com as your Delivery option, use the JSON File to create complete all of the relevant information that you are requested.


The last part of the set-up will be to define the folder pattern you want to use. You can use any Creative Force property to create the folder structure you are after.

Equally, if you have varients set up, you can specify how varients are handled as well as non-selects.

If Creative Force finds an existing file in your Box account, you can choose whether you replace the existing files, or keep both.


Once you are done, you can start assigning this asset delivery location to the appropriate workflows!

Did this answer your question?