WoodWing - inriver Integration and Automation

Common Integration Use Cases Between WoodWing and inriver

WoodWing and inriver complement each other well in organizations that need strong product information management alongside rich digital asset management. inriver can serve as the system of record for product data, while WoodWing manages the approved images, videos, campaign assets, and publishing files that bring that product data to life across channels.

1. Sync approved product images and videos from WoodWing to inriver

Direction: WoodWing to inriver

Marketing or content teams manage master product photography, lifestyle images, and product videos in WoodWing, then publish approved assets to inriver for use in product records. inriver users can attach the correct asset set to each SKU, variant, or product family without searching across multiple file repositories.

Business value: Ensures product pages, partner portals, and e-commerce channels always use approved, current media. Reduces manual file handling and lowers the risk of outdated or incorrect imagery being published.

2. Enrich product records in inriver with campaign-ready creative from WoodWing

Direction: WoodWing to inriver

When a new product launch or seasonal campaign is prepared in WoodWing, the final creative assets, banners, hero images, and promotional videos are pushed into inriver and linked to the relevant products. Product managers and marketers can then reuse those assets in channel-specific product content and launch materials.

Business value: Speeds up product launch execution and keeps campaign messaging aligned with product data. Improves collaboration between brand, marketing, and product teams.

3. Publish localized product content with region-specific assets

Direction: Bi-directional

inriver manages localized product descriptions, attributes, and market-specific product hierarchies, while WoodWing stores localized images, translated brochures, and region-specific videos. The integration can match assets to the correct market, language, or channel so each region receives the right combination of product data and media.

Business value: Supports global commerce and reduces localization errors. Helps teams launch products faster in multiple markets with consistent but regionally relevant content.

4. Connect product variants and asset renditions for channel publishing

Direction: Bi-directional

inriver maintains product families, variants, and relationships, while WoodWing provides the corresponding master assets and renditions such as web-optimized images, print-ready files, and video formats. The integration can automatically associate the correct asset version with each product variant or distribution channel.

Business value: Improves channel accuracy and reduces the manual work of resizing, renaming, and reattaching assets. Ensures each channel receives the right format for its technical requirements.

5. Support print catalog and brochure production with product data and assets

Direction: inriver to WoodWing, with asset return from WoodWing to inriver

inriver provides structured product data, specifications, and pricing information to WoodWing for use in catalog, brochure, and editorial layouts. WoodWing then manages the layout files, page proofs, and final publication assets, which can be linked back to inriver for reference and reuse.

Business value: Streamlines print production and reduces rekeying of product information. Helps marketing and publishing teams produce accurate catalogs faster with fewer revisions.

6. Centralize museum or heritage collection media with structured item metadata

Direction: WoodWing to inriver

For museums and heritage organizations, WoodWing stores high-resolution images, archival videos, and digitized collection media, while inriver holds structured item metadata such as object name, category, provenance, and exhibition context. The integration links media assets to collection records so curators and content teams can publish consistent item information across websites, digital exhibits, and partner portals.

Business value: Improves discoverability and governance of collection content. Reduces duplicate asset storage and makes it easier to publish accurate cultural and educational content.

7. Automate asset approval and publishing workflows for product launches

Direction: Bi-directional

WoodWing manages review and approval of images, videos, and creative files, while inriver tracks product readiness and channel publication status. Once assets are approved in WoodWing, they can be automatically flagged as ready in inriver, enabling downstream teams to publish complete product content only when both data and media are approved.

Business value: Creates a controlled launch process and reduces the risk of incomplete or unapproved content going live. Improves accountability across creative, product, and e-commerce teams.

8. Reuse event and marketing media across product and brand content

Direction: WoodWing to inriver

Photos and videos from trade shows, product demonstrations, company events, and brand campaigns are stored in WoodWing and selectively linked to relevant products in inriver. This allows teams to enrich product detail pages, partner materials, and sales enablement content with real-world media that supports the product story.

Business value: Increases content reuse and strengthens product storytelling. Helps marketing teams maximize the value of event and campaign media across multiple channels.

Overall, integrating WoodWing and inriver creates a strong content supply chain where inriver governs product information and WoodWing governs rich media and publishing assets. Together, they help organizations publish more complete, accurate, and channel-ready product content with less manual effort.