Build a Bynder to Salsify workflow with OneTeg

See how OneTeg’s AI flow builder, Teggy, creates a workflow that matches product images in Bynder with the right products and image fields in Salsify.

Start with product images in Bynder

The video begins with a collection of product images in Bynder. Each asset has a SKU and an image angle, such as Front, Side, or Back. These details identify the product the image belongs to and where it should appear on that product’s record.

The matching products already exist in Salsify, but their image fields are empty. Assigning the images requires a process that can read the asset metadata, find the correct product, and place each image in the right field.

Describe the workflow to Teggy

In OneTeg, the user describes that process to Teggy: retrieve the images from Bynder, match them to Salsify products by SKU, and assign each image according to its angle.

Teggy builds a workflow with the steps needed to carry out the request. The flow checks that an asset has the required metadata, looks for an existing digital asset in Salsify, and creates one when needed. It then finds the matching product by SKU and updates the appropriate image field.

The generated flow is visible in OneTeg. The team can review its steps, request changes, and approve it before running it.

Run the flow and check the result

Once the flow runs, OneTeg processes the Bynder assets and matches them to the corresponding Salsify products. The workflow view shows its progress as each step completes.

Back in Salsify, the product record now displays its Front, Side, and Back images in the correct fields. The images are associated using the SKU and image angle stored with each asset.

OneTeg also records the run, giving the team a way to check its status and review what happened.

Use the same process for new product images

Bynder manages the source images and their metadata. Salsify holds the product records. OneTeg handles the matching and assignment between them.

The workflow gives teams a repeatable way to add product imagery without matching each asset and updating each field by hand. It also shows how a request described in OneTeg becomes a workflow that teams can review, run, and monitor.

To see other systems OneTeg can connect, visit OneTeg’s connector library.