Bynder is a leading digital asset management (DAM) platform used by global brands to centralize, organize, and distribute creative content. VNTANA and Bynder have partnered on a standard integration that automatically syncs 3D assets from the VNTANA Platform into Bynder, including both the original source file and the optimized formats, while preserving key metadata.
The VNTANA integration for Bynder is designed to keep your 3D content discoverable in the same DAM your creative and marketing teams already use, and to replace Bynder’s standard asset viewer with an interactive VNTANA 3D viewer via a Chrome extension. To view our guide on VNTANA tagging and metadata setup, view the VNTANA Platform Comprehensive Feature Guide.
Integration Overview
Downloads
Bynder Vntana 3D Viewer Chrome Extension
Using the Integration
The VNTANA Bynder integration is built and maintained by Bynder as a Standard Integration available from within the Bynder portal. Once configured, the integration runs automatically and pulls any VNTANA Asset tagged with the trigger tag (or tags) you define. The Chrome extension is a separate, one time install per user that enables the in browser 3D viewer.
If you don’t see Vntana listed under Standard integrations in your Bynder Integrations Hub, it hasn’t been enabled on your instance yet. Contact your Bynder Customer Success Manager (CSM) and ask them to enable the VNTANA integration for your organization. Once enabled, it will appear in the Integrations Hub and can be configured following the steps below.
Getting Access
If you don’t see Vntana listed under Standard integrations in your Bynder Integrations Hub, it hasn’t been enabled on your instance yet. Contact your Bynder Customer Success Manager (CSM) and ask them to enable the VNTANA integration for your organization. Once enabled, it will appear in the Integrations Hub and can be configured following the steps below.
Prerequisites
A set of prerequisites should be in place before configuring:
- An active VNTANA account with API access enabled.
- The VNTANA integration enabled on your Bynder instance by your Bynder CSM (see Getting Access above).
- A Bynder portal with admin access to Advanced Settings.
- A VNTANA Authentication Key (see the guide for instructions on generating one).
- The Bynder Vntana 3D Viewer Chrome extension for any user who needs to view assets in 3D.
Authentication
To make use of the integration you must first authenticate Bynder with the VNTANA Platform using a valid Authentication Key. The Authentication Key is generated from your VNTANA account and pasted into the Bynder integration configuration during setup. Once authenticated, the integration uses the key to register a webhook against the selected Organization and Workspace(s), and no additional re-authentication is required for ongoing syncs.
Configuration Home
The Bynder Integrations Hub serves as the home for the VNTANA integration. To reach it:
- Gear Icon located in the upper right corner of the Bynder portal. Navigate to Advanced Settings > Portal Settings.
- Integrations Hub located in the left navigation panel. Select Browse Integrations.
- Vntana found in the list of Standard integrations. Press Configure to open the setup modal.
Configuring will present a number of steps in which you will set the parameters of the sync to ensure the correct assets are connected between VNTANA and Bynder.
Integration Name
The Integration Name is a free text field that allows you to label the integration however your team prefers. This is helpful if your organization runs multiple VNTANA Workspaces or wants to label the integration by team, region, or product line.
Connections
The Connections panel houses the two credentials the integration needs to function:
- Bynder Connection requires the full URL associated with your portal, including https://. Example: https://your-domain.bynder.com.
- Vntana Connection requires the VNTANA Authentication Key generated from the VNTANA Platform.
Organization and Workspace
Once both connections are made, you select the VNTANA Organization and (optionally) Workspace the integration should pull from.
- Organization is required.
- Workspace is optional. Leaving it blank means the integration will track all Workspaces within the selected Organization.
Trigger Tags
The integration uses a Trigger Tag (or tags) added to your VNTANA Assets to determine which assets are pulled into Bynder. This is the primary control for what shows up in the DAM.
- A Trigger Tag is any Tag you add to an Asset on the VNTANA Platform.
- Multiple tags can be entered as a comma separated list.
- The match logic is match all, meaning an Asset must have every tag in the list to be pulled. Use a single tag if you want a broader sync.
Metadata Mapping
The final step in the setup modal allows you to map VNTANA Asset properties to Bynder metadata properties. This ensures that information such as Vntana Product URL, Vntana Product UUID, Vntana Client Slug, and Vntana Organization Slug is carried over and visible in Bynder’s asset info panel.
File Sync
Sync is webhook driven and user triggered. When a tagged Asset is published to Live Public on the VNTANA Platform, the webhook fires and Bynder pulls both the original source file and the optimized formats. Both are stored against the Bynder asset so downstream users can grab whichever format they need. Assets that are not published to Live Public will not be pulled, regardless of whether they carry the Trigger Tag.
iFrame Viewer Setup
The standard Bynder asset viewer does not natively render interactive 3D. To replace it with the VNTANA viewer, Bynder has built a Chrome extension that swaps in the VNTANA iFrame whenever an asset with a VNTANA iFrame URL is opened.
- Chrome Extension install the Bynder Vntana 3D Viewer extension from the Chrome Web Store.
- Target Domain open the extension popup and enter the domain Bynder is served from (for example, bynder.com or portal.mycompany.com). Press Update Domain.
- Current Domain confirms the domain the extension is currently watching.
Asset View in Bynder
Once an asset has been pulled into Bynder and the Chrome extension is installed, the standard Bynder asset detail page is augmented with the VNTANA viewer and metadata.
- Interactive 3D Viewer replaces the standard image preview, allowing users to rotate, zoom, and inspect the asset in browser.
- Open File in Vntana Platform a direct deep link from Bynder back into the VNTANA Platform for editing, optimization, or sharing.
- VNTANA Metadata Fields include Vntana Product URL, Vntana Product UUID, Vntana Client Slug, and Vntana Organization Slug, alongside Bynder’s native fields.
- Download all files Bynder’s standard download action returns all synced files (original and VNTANA optimized formats) in a single bundle.
Integration Operations and Possible Issues
Asset Not Syncing
Sync only fires when a tagged Asset is published to Live Public. If an Asset is tagged correctly but not appearing in Bynder, confirm the Asset is in Live Public status on the VNTANA Platform. Drafts, internal, and link only assets will not trigger the webhook. It is also worth noting that webhooks do not trigger retroactively, meaning an asset that was already Live Public at the time the integration is configured will not trigger it without manual intervention.
Tag Changes
If a Trigger Tag is removed from an Asset on the VNTANA Platform, that Asset will no longer be pulled by the integration. Existing assets already in Bynder are not automatically deleted, but they will stop receiving updates from VNTANA. We recommend establishing a clear tagging convention before turning the integration on.
Match All Logic
Because the Trigger Tag matcher uses match all logic, adding a second tag to the integration narrows the set of assets that sync rather than expanding it. If syncing fewer assets than expected, check the tag list against what is actually applied on each Asset.
Chrome Extension Not Replacing Viewer
If the standard Bynder viewer is still appearing instead of the VNTANA viewer, check:
- The extension is installed and enabled in Chrome.
- The Target Domain in the extension matches the domain you are viewing Bynder on.
- The Asset in Bynder has a VNTANA iFrame URL populated (it will if it was synced via the integration).
Re-Authenticating
If the integration stops pulling new assets, the most common cause is an expired or rotated VNTANA Authentication Key. Generate a new key from the VNTANA Platform and update it in the Bynder Integrations Hub > Vntana > Configure.
How the Integration Communicates
The integration syncs by registering a webhook within VNTANA that tracks the indicated Workspace(s). The webhook fires when an Asset is published to Live Public, and Bynder then pulls the original and optimized files server to server. This sync traffic flows directly between VNTANA and Bynder and does not traverse the end user’s network.
End user network traffic does occur in two scenarios: loading the VNTANA iFrame inside the Bynder asset viewer, and downloading models from Bynder. If your IT and Security teams have outbound traffic restrictions on the user network, the following domains should be allowed:
- ***.vntana.com**
- `storage.googleapis.com`
Authentication between Bynder and VNTANA is handled via the VNTANA Authentication Key entered during configuration. No additional firewall changes are required on the VNTANA side.