How to enable Bynder Content Connector

Updated January 27, 2026 20:40

This article guides you through the setup of the Bynder integration.

Prerequisites

Admin/owner access to the Templafy tenant.
Content Connectors modules enabled.
An OAuth application registered in Bynder.

Register OAuth App in Bynder

In your Bynder environment, register an OAuth application via Settings > Advanced Settings > Portal settings > OAuth Apps.
Select Grant Type:
- Authorization Code + Refresh Token: This will allow users to log in to their own Bynder accounts and access user-specific content.
- Client Credentials: This will authenticate using an application identity (service-to-service), meaning no end-user login is required and all users will see the same available Bynder content.
If Grant Type is set to Authorization Code + Refresh Token, set the Callback URL (Authorization redirect URL) to: https://public.templafy.com/integrations/oauth/login-callback .
Ensure the following scope remains checked: asset:read.
Save the changes to generate a Client ID and Client Secret.

Configure Bynder connector in Templafy

Go to Integrations section.
Go to Available tab.
Search for "Bynder V2".
Click +.
Fill out the necessary configuration fields:
- Display Name (required).
  - The name entered in this field will be displayed to the end-users.
- Base URL (required).
  - The first part of your URL when accessing Bynder (https://mycompany.bynder.com/).
Select desired Authentication type.
- OAuth 2 Authorization Code requires a user login and displays user specific content.
- OAuth 2 Client Credentials does not require login and displays the same content to all users.
Based on the selected Authentication type, fill out the necessary configuration fields.
- For OAuth 2 Authorization Code:
  - Client ID.
  - Client Secret.
- For OAuth 2 Client Credentials:
  - Client ID.
  - Client Secret.
Hit Save.

Important

The Bynder content connector can have only one authentication type at a time. If several authentication types are required, several connectors should be set up.

Note

If the Bynder Content Connector is utilizing OAuth 2 Authorization Code as an authentication type, the following should be noted:

When not logged in, the user will not be able to access any Bynder content; the content will only be displayed once the login has been successful.
If the user is already logged in on the Bynder side, the log in on Templafy's side will be seamless as the token already exists.
If the user isn't already logged in on the Bynder side, the user will need to provide Bynder credentials to log in as the token cannot be found.
If a user has multiple Bynder accounts and needs to switch between these accounts, this can be performed by logging out and logging in again within the same browser, OR by opening a different browser (or incognito) and logging in with the desired account.

Related to

connector connectors dam admin_role

Articles in this section