Skip to main content

Salsify integration

Automatically sync and assign assets to your products

Updated yesterday

This integration ensures that the right, most up-to-date assets from Frontify are automatically assigned to the correct products in Salsify – based on a shared product identifier.

It is designed for product content managers, PIM administrators, and brand/DAM teams who want Frontify to remain the single source of truth for assets, while Salsify continues to manage product data.


What this integration does

Once configured, the integration:

  • Reads assets and asset metadata from Frontify

  • Matches them to Salsify products using a defined product identifier (e.g., sku)

  • Assigns or updates assets in specific Salsify asset properties

  • Runs automatically on a defined schedule (e.g., every 12 hours or daily)

This removes manual asset uploads, reduces errors, and ensures consistency across systems.


How it works (in simple terms)

  1. Each Salsify product has a unique identifier (for example: sku).

  2. The same identifier value must exist on the related Frontify asset (stored as a metadata text field).

  3. The integration looks at specific metadata on the Frontify asset that is being used for Salsify's asset property. Based on your defined mapping, it assigns the asset to the correct Salsify asset property.

Example:

If a Frontify asset has:

  • Identifier (e.g. sku): ABC-123

  • Asset mapping: Additional Images

And in Salsify you have a product with:

  • sku = ABC-123

The integration will:

  • Match the asset to the product

  • Assign it to the Salsify property mapped to Additional Images (for example images)


Capabilities

1. Identifier-based matching

Assets are matched to products using a configurable identifier field (e.g., sku).

  • You can have one or multiple identifiers per asset.

  • Matching is exact (case- and space-sensitive)

2. Flexible property mapping

You decide which Frontify metadata values correspond to which Salsify asset mapping.

Example mapping:

  • Main ImageMain Image

  • Bottom ImageBottom Image

  • Additional Imagesimages

This means:
When a Frontify asset contains the metadata value Additional Images, the integration writes that asset into the Salsify images property.

3. Handling multiple assets

  • Multiple Frontify assets can be assigned to the same product and property.

  • All asset fields are treated as multi-value fields, meaning new assets are always appended rather than replacing existing values.

4. Scheduled sync

The integration runs automatically on a schedule you define:

  • Daily

  • Every 12 hours

  • Or another configured interval, but not more than once per hour

Each run processes assets and updates assignments in Salsify.

5. One-way sync

Assets flow from Frontify → Salsify.
Frontify remains the source of truth for assets. Changes made directly in Salsify may be overwritten during the next sync.


What you need before setup

Frontify

  • Frontify domain

  • API token

    • The token inherits the permissions of the user who created it

    • Ensure the user has access to all relevant libraries, assets, and metadata fields

Salsify

  • Salsify domain

  • API token

  • A product identifier field (e.g., sku)

    • Must be a text field

    • Must contain values that also exist in Frontify

    • Matching is case-sensitive and space-sensitive

Mapping definition

You must define:

  • Which Frontify metadata values should trigger assignment

  • Which Salsify asset properties they should populate


How to use the integration

Step 1 – Define your product identifier

Choose the Salsify field that uniquely identifies products (e.g., sku).

Important:

  • The same identifier value must be added to the corresponding asset in Frontify.

  • The value must match exactly (including capitalization and spacing).


Step 2 – Prepare your Frontify metadata

In Frontify:

  1. Ensure assets contain:

    • The product identifier value

    • The metadata values used for mapping (e.g., Main Image, Additional Images)

  2. Confirm metadata names match exactly what is defined in the mapping.


Step 3 – Configure your mapping

Your mapping defines how Frontify metadata maps to Salsify asset properties.

Example:

"Main Image": "Main Image", "Bottom Image": "Bottom Image", "Additional Images": "images" 

Meaning:

  • If a Frontify asset contains metadata Main Image, assign it to the Salsify property Main Image.

  • If it contains Additional Images, assign it to the Salsify property images.

You can include as many mappings as needed.


Step 4 – Set your sync schedule

Choose how often the integration should run:

  • Daily (recommended for most teams)

  • Every 12 hours

  • Or another defined interval

The integration will then:

  • Fetch updated assets from Frontify

  • Match them to products

  • Assign or update the mapped Salsify fields


Error handling

  • Assets without a valid identifier are skipped

  • Assets with no matching product in Salsify are ignored

  • Invalid mappings (e.g. missing Salsify properties) prevent assignment


Limitations

  • Matching is exact (case- and space-sensitive)

  • Sync is one-way (Frontify → Salsify only)


After setup

Once configured and running:

  • Assets in Frontify are automatically reflected in Salsify

  • Product records stay up to date without manual uploads

  • Teams can manage assets centrally in Frontify while Salsify handles product data

Did this answer your question?