Integrate Bynder

9 min

You can integrate Bynder with Optimizely Content Marketing Platform (CMP) to publish assets, send assets to Bynder, and retrieve assets from Bynder through the embedded Bynder Asset Picker, letting you seamlessly pull Bynder-managed assets directly into CMP.

The Bynder Standard Integration for CMP enables teams to publish assets—such as images, videos, and various other file types—from CMP into Bynder with the appropriate labels, tags, and metadata. When published, the integration keeps assets synchronized across their full lifecycle, including create, update, and delete actions, ensuring consistency between CMP and Bynder.

Integration features

Have a uni-directional integration from CMP to Bynder.

Use label-based publishing.

Publish assets one at a time or in bulk.

Publish asset metadata with the assets.

Publish assets to Bynder's waiting room.

Upload new version of assets from CMP to Bynder.

Update assets metadata (title and labels) to have it reflected in Bynder.

Publish hardcode metadata for all assets from CMP to Bynder.

Delete assets in CMP and remove them from Bynder.

Requirements

Cloud-based Bynder Instance

A Bynder Service account supporting OAuth 2.0

Admin access to Bynder

Configure Bynder

You need the following to configure the Bynder integration:

Access to your Bynder instance – To roll out and test the integration, the developers need access to your Bynder production instance or a developer instance if available (recommended).

Create a Bynder service account – You must create a service account in Bynder with administrator access. This main account makes API calls from CMP to your Bynder platform. The integration ties actions performed to the service account user. Create the service account user and use an identifiable name, such as CMP Service Account. The service account must have Admin access.

Set up OAuth 2.0 in Bynder – You can do this in Bynder in the API section under Integration (Admin permissions required).

Register a CMP Application – The application manages the authentication of the CMP service account to make API calls. See Obtain the Client ID and Secret to register your client application for guidelines to configure.

Configure integration Webhooks – You must configure a publishing webhook for the integration to get the updates from the library. Fill out the following information, and subscribe the webhook to library-specific events.

You can publish assets from CMP to Bynder by appending a publishing label.

Label publishing

You can use a label to publish CMP assets to Bynder, such as a label group called "Asset Destination" and a label value of "Bynder". You must configure the label in CMP. The following process shows how to set up a publishing label.

Go to your Fields settings page.

Click Add Field. The Create a New Field view displays.

Fill out the Create a New Field view as follows:

Select Label for Field Type.

Select Single-Select (preferred) or Multi-Select.

Enter an intuitive name in the Field Name (Example: Asset Destination) so your publishers and users know what this label is used for.

When you add a publishing label to an asset in the Library, CMP automatically sends the asset to Bynder. You can also add the label while working in a task. As long as you move the labeled asset from the task to the Library, CMP publishes it to Bynder.

Label publishing from a task

Add the publishing label to the assets you want to send to Bynder.

Ensure the asset is sent to the library.

Complete the task.

After the asset is in the library with the publishing label, it is pushed to Bynder.

Publishing assets with tags

For labels to be sent as tags to Bynder with assets, align the taxonomy between the CMP and Bynder. You must create Bynder tags as labels in the CMP.

Appending label on the CMP side

Tags appended on the Bynder side

Hardcode asset metadata

You can also hardcode recurring metadata to assets. If you need to add metadata to all assets published from CMP to Bynder, you can add those programmatically instead of manually. When you publish the assets from CMP to Bynder, they contain the fixed metadata.