Bynder – Inriver connector

The connector synchronises asset metadata in both directions between Bynder and Inriver Resource entities.

                        What you can do

Q&A

Answers to the questions we hear most, from first setup to day-to-day operation. The same questions and answers are in the integration manual.

1. Scope and bidirectional sync
2. Linking assets to entities
3. Importing from Bynder
4. Sending to Bynder
5. Setup and platform

Scope and bidirectional sync

1. What does the bidirectional sync cover?
   It synchronises asset metadata between Bynder and the Inriver Resource entity. Bynder to Inriver: the asset file, asset properties and metaproperty values are written to Resource fields, and links to other entities are created. Inriver to Bynder: the values of mapped Resource fields are written to Bynder metaproperties on the same asset.
2. Can metadata from non-Resource entities (for example Item) be sent to Bynder?
   Not supported. Only values held in Resource fields are synchronised to Bynder. To show product or item data on an asset, use an Inriver expression to copy the value from the linked entity to a Resource field, then map that Resource field to a Bynder metaproperty. An expression lets you decide which value is stored on the Resource and sent to Bynder, also when the Resource is linked to several entities.
3. Can several products be linked to one asset?
   Yes, as links. One asset is one Resource, and that Resource can be linked to many entities through the filename pattern or through AUTOMATIC_LINK_MAPPING. The Resource holds one value per field, so a Bynder metaproperty receives one set of values per asset. A different value per linked product cannot be stored on the same asset.
4. Can several assets be combined into one Resource?
   No. Every Bynder asset is stored as its own Resource.
5. Does Bynder data change my product records?
   No. Inbound sync writes to the Resource entity only. On other entities it creates or removes links and never changes field values.
6. Which Resource fields are sent to Bynder?
   The fields listed in the outbound METAPROPERTY_MAP, written as {Bynder metaproperty ID}={Resource field ID}. Name these Resource fields with the prefix Resource, for example ResourceDescription. The Resource must already have a Bynder asset ID and a download or upload state of done. CVL keys are sent, not display values, and multivalue CVL fields are not supported outbound.
7. When are the values sent?
   The Worker extensions send the mapped Resource field values when a Resource is changed in Inriver, and when its links change.
8. How is the Inriver to Bynder feed set up?
   The BynderAssetWorkerEntities (EntityListener) and BynderAssetWorkerLinks (LinkListener) extensions send the values of mapped Resource fields to Bynder through the Bynder REST API when Resource entities or their links change in Inriver.
9. Can two Inriver fields be combined into one Bynder metaproperty?
   Each Bynder metaproperty is mapped to exactly one Inriver field. To send the content of two fields as one value, combine them in a single Resource field, for example with an Inriver expression, and map that field. Other combinations need a custom solution, which Ctac can discuss with you.

Linking assets to entities

1. How is the link between a Bynder asset and an Inriver entity established?
   Primarily through REGULAR_EXPRESSION_FOR_FILENAME: named groups match field values on Inriver entities. Additionally, AUTOMATIC_LINK_MAPPING creates one-to-many relationships based on Bynder metadata.
2. What is LinkTypeId in AUTOMATIC_LINK_MAPPING?
   The Inriver link type that the connector creates between the found entity and the Resource, for example ItemResource or ProductResource.
3. What data type should be used for multi-value link fields?
   Use a String field in Inriver such as ItemNumber, ItemEAN or EntityId. For multi-value text properties in Bynder, use the Long text type and set SplitCharacters in the AUTOMATIC_LINK_MAPPING entry, for example , or ; or ,;, so the connector splits the value before matching.
4. Do I need to change the separator when a Bynder metaproperty holds several values?
   No. The connector reads each value of the metaproperty. When one text value holds several entries, set SplitCharacters in the AUTOMATIC_LINK_MAPPING entry to the characters your values use, for example , or ;. The connector splits the text on those characters and trims every entry before matching. It does not convert one separator into another.

Importing from Bynder

1. How often are assets synchronised from Bynder to Inriver?
   After each SNS notification (create, update, archive, delete), an update is sent. BynderAssetNotifyProcessor processes these up to every 15 minutes. There is no automatic full sync; trigger it manually via BynderAssetLoader.
2. What is the maximum sync delay from Bynder to Inriver?
   Up to 15 minutes via BynderAssetNotifyProcessor. Click Run on the processor to process pending notifications immediately.
3. What is the maximum sync delay from Bynder to Inriver?
   Up to 15 minutes via BynderAssetNotifyProcessor. Click Run on the processor to process pending notifications immediately.
4. Can we resend all data for all assets (full load)?
   Yes. Click Run on BynderAssetLoader. It loads the assets that match INITIAL_ASSET_LOAD_URL_QUERY and IMPORT_CONDITIONS. It never runs on a schedule.
5. How do we control which assets are imported?
   Use IMPORT_CONDITIONS to filter on any Bynder asset property or metaproperty. Conditions are combined with AND. To accept an asset when one of several sets of conditions is met, give the conditions a group: conditions in the same group are combined with AND, and the groups are combined with OR. Leave the setting empty to import all assets. A new installation is pre-filled with a condition on the metaproperty synctoinriver, so create that metaproperty or replace the condition. The group option is available in connector versions from October 2026.
6. What happens if two Bynder assets have the same filename or title?
   Bynder filenames are not unique. The file is stored in Inriver under its original name; if a unique field or file name already holds that value, Inriver rejects it and the asset is not imported. The log shows: Trying to add entity with unique field where the data already exists.
7. What happens when an asset is archived in Bynder?
   Use FIELD_VALUES_TO_SET_ON_ARCHIVE_EVENT to update Resource fields, for example an archived flag or an archive date. To delete the Resource on archive, set both DELETE_RESOURCE_ON_ARCHIVE_EVENT and DELETE_RESOURCE_ON_DELETE_EVENT to True.
8. What happens when an asset is deleted from Bynder?
   It depends on DELETE_RESOURCE_ON_DELETE_EVENT. If True, the Inriver Resource is deleted. If False (default), the Resource remains in Inriver.
9. What if a new Bynder metaproperty value does not exist as a CVL key in Inriver?
   If CREATE_MISSING_CVL_KEYS = True, a new CVL key is auto-created using the Bynder database name. A Bynder admin should then add a readable display label.
10. Will there be one Resource per image URL?
    No. One Bynder asset is one Resource. The URLs of the derivatives (image sizes) are stored in separate fields on that Resource. Map each one in ASSET_PROPERTY_MAP as thumbnails.{derivative}={FieldTypeId}, for example thumbnails.thul=ResourceThumbnailURL. Using several derivatives is common when channels need different image sizes.
11. Will there be one Resource per image URL?
    No. One Bynder asset is one Resource. The URLs of the derivatives (image sizes) are stored in separate fields on that Resource. Map each one in ASSET_PROPERTY_MAP as thumbnails.{derivative}={FieldTypeId}, for example thumbnails.thul=ResourceThumbnailURL. Using several derivatives is common when channels need different image sizes.
12. Can I store a Bynder derivative instead of the original file?
    Yes. Set DOWNLOAD_THUMBNAIL_TYPE to the derivative name, for example thul or webimage. For videos, use DOWNLOAD_VIDEO_TYPE. Leave empty to download the original, which must be marked public in Bynder.
13. Do we need a CDN between Bynder and our e-commerce platform to use the image URLs?
    No separate CDN is needed for the connector. The Bynder URL is stored on the Resource, and an Inriver channel can pass it on to the e-commerce platform as an attribute.
14. Are failed messages automatically retried?
    Partly. When Bynder reports that an asset cannot be found (HTTP 404), the notification stays queued and is retried at every run of BynderAssetNotifyProcessor until RETRY_FAILED_NOTIFICATIONS_EXPIRES_AFTER has passed (default 7 days). Other failures are not retried. Run BynderAssetLoader manually to reprocess all assets. Available in connector versions from June 2026. In earlier versions failed messages are not retried.

Sending to Bynder

1. Are CVL keys or values pushed from Inriver to Bynder?
   CVL keys are pushed, not display values. If a key does not exist in the Bynder metaproperty, it will be auto-created. Display values are managed in Bynder. Note: multivalue CVL is not yet supported outbound.
2. How do we choose which Resources are sent to Bynder?
   Metadata is sent for Resources that already have a Bynder asset ID, through the outbound METAPROPERTY_MAP. A new file is uploaded only when OUTBOUND_INTEGRATION = True, the Resource matches EXPORT_CONDITIONS and ResourceBynderUploadState = todo. Uploads also need BYNDER_BRAND_NAME.

Setup and platform

1. Can multiple Inriver environments connect to one Bynder portal?
   Yes, but only one environment should be active at a time. Disable the test environment connection before activating production. After go-live, perform a full sync by running BynderAssetLoader.
2. Is OAuth2 supported?
   Yes. OAuth2 is the recommended method. Set AUTHENTICATION_TYPE = OAuth2 and provide CLIENT_ID and CLIENT_SECRET. OAuth1 remains available for existing deployments.
3. Is DAT (Dynamic Asset Transformation) supported?
   Yes, limited support. The DAT base URL can be stored in Inriver. Data consumers append the specific DAT transformation parameters to this URL.
4. Is the use of different Inriver segments supported?
   No. Assets are stored in the default Inriver segment.
5. What is the Bynder image URL structure?
   Original: https://YourPortalURL.com/m/{idhash}/original/{asset-name}.{ext}. Derivative: https://YourPortalURL.com/m/{idhash}/{derivative-prefix}-{asset-name}.{ext}. A custom domain for your Bynder portal changes the host name only; the structure stays the same.
6. How are first and second line support organised?
   Bynder provides first line support through its support desk. Ctac, as Inriver partner, provides second line support and manages the roadmap of the connector.
7. Is more architectural and technical documentation available?
   Yes. The integration configuration manual covers installation, configuration and operation of every setting. For architecture details, contact Ctac.