Integrate Bynder with Tridion Sites – Bynder Support

Would you like to add your Bynder assets to your Tridion Sites? Save yourself the time of uploading your assets twice and start using the the Tridion Sites integration. The integration allows you to use your Bynder assets directly in Tridion Sites. You can also search for your assets using keywords and navigate through the different result pages. The integration follows our API Rate Limiting policy.

Skip directly to

Supported versions
Derivatives used
Installation and configuration
Use the plugin

Watch a video

Prerequisites

Before you install the plugin, you need to have the following things set up:

A working Bynder account
API tokens - see Create API tokens for your app
Derivatives - see Get started with image derivatives

Supported versions

The following versions are supported:

Tridion Sites 2013 SP1
SDL Web 8.1/Tridion Sites Sites 8.1
SDL Web 8.5/Tridion Sites Sites 8.5
Tridion Sites Sites 9
Tridion Sites Sites 9.1
Tridion Sites Sites 9.5

Derivatives used

Currently, derivatives are not supported. Tridion Sites downloads the original files from Bynder.

Installation and configuration

Download the plugin here. Alternatively, you can download the plugin from the SDL appstore. Next, do the following in your SDL environment:

Create a Stub folder named Bynder Provider in SDL under <Root Publication> (or the selected Publication in the BluePrint hierarchy)> Building Blocks > Default Templates > SDL External Content.

For example: 000 Empty > Building Blocks > Default Templates > SDL External Content.
Copy the folder's TCM URI (also known as Content Manager URI, see SDL documentation). You will need it later on.
Create a directory called BynderProvider under C:\ProgramData\SDL\Tridion Sites\External Content Library\AddInPipeline\Addins\
Copy the compiled DLLs to the directory from step 3. You can do it manually or using Visual Studio.
Go to SDL Web home directory\SDL Web\config and open your ExternalContentLibrary.xml.

In the ExternalContentLibrary.xml add the following code replacing all the variables in [] with values:

<MountPoint type="BynderProvider" id="bynder" rootItemName="Bynder">
		<StubFolders>
			<StubFolder id="tcm:2-37-2" />
		</StubFolders>
		<PrivilegedUserName>TRIVIDENT01\Administrator</PrivilegedUserName>
		<EnvironmentUrl xmlns="ecl:BynderProvider">https://trivident.getbynder.com</EnvironmentUrl>
		<ConsumerKey xmlns="ecl:BynderProvider">...</ConsumerKey>
		<ConsumerSecret xmlns="ecl:BynderProvider">...</ConsumerSecret>
		<TokenKey xmlns="ecl:BynderProvider">...</TokenKey>
		<TokenSecret xmlns="ecl:BynderProvider">..</TokenSecret>
		
		<AssetNotFoundPlaceholderId xmlns="ecl:BynderProvider">...</AssetNotFoundPlaceholderId>
		<DisplayMetaPropertyFolders xmlns="ecl:BynderProvider">enabled</DisplayMetaPropertyFolders>
		<HideEmptyMetaPropertyFolders xmlns="ecl:BynderProvider">disabled</HideEmptyMetaPropertyFolders>
		<AdditionalMediaPropertiesToShow xmlns="ecl:BynderProvider">views,dateCreated</AdditionalMediaPropertiesToShow>
	</MountPoint><MountPoint type="BynderProvider" id="bynder" rootItemName="Bynder Provider">
<StubFolders>
	<StubFolder id="[STUB FOLDER TCM-URI]" />
</StubFolders>
<PrivilegedUserName>[SDL ADMIN USER]</PrivilegedUserName>
<EnvironmentUrl xmlns="ecl:BynderProvider">[YOUR ENVIRONMENT URL, for example: https://myportal.bynder.com]</EnvironmentUrl>
<ConsumerKey xmlns="ecl:BynderProvider">[BYNDER USER'S CONSUMER KEY]</ConsumerKey>
<ConsumerSecret xmlns="ecl:BynderProvider">[BYNDER USER'S CONSUMER SECRET]</ConsumerSecret>
<TokenKey xmlns="ecl:BynderProvider">[BYNDER USER'S TOKEN KEY]</TokenKey>
<TokenSecret xmlns="ecl:BynderProvider">[BYNDER USER'S TOKEN SECRET]</TokenSecret>
</MountPoint>

Optional parameters

AssetNotFoundPlaceholderId

Bynder ID of the asset to be used as a placeholder in case the asset selected by a component is not available in Bynder anymore (used to cause a bug so that the component could not be opened).

DisplayMetaPropertyFolders

Configuration that enables the folder structure constructed from Bynder Meta Properties. Disabled by default to provide backwards compatibility and the same behavior as the old version.

HideEmptyMetaPropertyFolders

Configuration that enabled hiding of empty folders. Requires extra querying and makes the interaction slower for large Bynder portals. Disabled by default.

AdditionalMediaPropertiesToShow

Coma separated list of additional media properties that will be exposed as external metadata. The property names come from Bynder SDK and can be looked up there if needed.

AlwaysUseOriginalFileForVideoPublishing

Setting this option to true should result in returning the original files.

AlwaysUseOriginalFileForImagePublishing

Setting this option to true should result in returning the original files.

Note

If you are unsure how to generate Bynder consumer secret and token, see Create API tokens for your app.

Apply the filtering hotfix. Do the following:
1. Go to %SDLWEB%\web\WebUI\Editors\ExternalContentLibrary\Extensions\Views
2. Create a backup the SiteEditEditor.Library.js file that you find in this location.
3. Copy the SiteEditEditor.Library.js file that is included in the plugin zip to %SDLWEB%\web\WebUI\Editors\ExternalContentLibrary\Extensions\Views
4. Open up the %SDLWEB%\web\WebUI\WebRoot\Configuration\System.config file.
5. In the attribute 'modification' in the <server> element increase the counter by one: <server version="8.5.0.22656" modification="21">
The hotfix should be active immediately. If you have XPM open in a browser you need to refresh the current browser tab.
Restart SDL services and verify that you can see the Bynder Provider folder and you can browse the assets in your environment through WebSDL.

Use the plugin

You can access your Bynder asset overview within Tridion assets by opening the Bynder Provider folder.
Use the Search box to search assets on keywords.
Click Toggle View to change to list view and filter the columns in your view.
When you use Bynder assets in SDL, we do not copy the asset but use its URL. In this way your CMS displays the latest version of the asset available in Bynder. To select an asset, open the Bynder Provider folder and select your asset.

Learn more