Home | Connectors | WoodWing | WoodWing - xConnector Integration and Automation

WoodWing - xConnector Integration and Automation

Integrate WoodWing Digital Asset Management (DAM) and xConnector apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between WoodWing and xConnector

1. Product image and video distribution to downstream commerce and PIM systems

Direction: WoodWing to xConnector

WoodWing can serve as the central repository for approved product photography, lifestyle images, and product videos, while xConnector can distribute those assets to product information management, eCommerce, and marketplace platforms. This ensures that only approved, current media is published across sales channels.

  • Marketing or product teams upload and approve assets in WoodWing
  • xConnector pushes selected files, metadata, and usage rights to downstream systems
  • Channel teams receive consistent, version-controlled media for product launches

Business value: Faster product content syndication, fewer manual uploads, and reduced risk of outdated or non-compliant assets being published.

2. Automated campaign asset delivery to marketing execution platforms

Direction: WoodWing to xConnector

Marketing teams can manage campaign images, banners, videos, and supporting creative assets in WoodWing, then use xConnector to distribute approved files to email marketing, CMS, social publishing, or digital advertising tools.

  • Campaign assets are tagged by region, brand, and channel in WoodWing
  • xConnector routes the correct asset versions to each execution platform
  • Updates in WoodWing can trigger replacement of outdated campaign files downstream

Business value: Improves campaign consistency across channels and shortens time from creative approval to live deployment.

3. Museum and heritage collection media synchronization

Direction: Bi-directional

For museums and heritage organizations, WoodWing can manage high-resolution images and videos of artifacts, exhibitions, and archival collections, while xConnector can synchronize metadata and asset references with collection management or public-facing digital catalog systems.

  • Curators enrich asset metadata in WoodWing
  • xConnector publishes approved media and descriptive fields to catalog or exhibit systems
  • Updates from collection systems can return identifiers or classification data to WoodWing

Business value: Creates a controlled workflow for digitized collections and improves access to accurate media across internal and public channels.

4. Publishing asset handoff for books, epubs, and layout production

Direction: Bi-directional

WoodWing is well suited for managing book content, photography, InDesign layouts, and epub-related assets. xConnector can integrate WoodWing with editorial production, content management, or distribution systems to move approved files into the next stage of publishing.

  • Editors and designers store final layouts and media in WoodWing
  • xConnector sends approved assets to print, digital publishing, or ebook production systems
  • Production status or revision feedback can be returned to WoodWing

Business value: Reduces production delays, improves version control, and supports coordinated print and digital publishing workflows.

5. Event media capture and internal content distribution

Direction: WoodWing to xConnector

Photos and videos from company events, trade shows, and internal communications can be stored in WoodWing and then distributed through xConnector to intranet portals, employee communications tools, or brand asset libraries.

  • Event teams upload raw and approved media into WoodWing
  • xConnector publishes selected assets to internal communication channels
  • Metadata such as event name, date, location, and usage rights is preserved

Business value: Makes event content quickly reusable across communications teams while maintaining governance and brand control.

6. Rights-managed asset delivery with approval-based publishing

Direction: WoodWing to xConnector

WoodWing can act as the system of record for approved assets and associated usage rights, while xConnector ensures only assets with valid permissions are sent to external systems. This is especially important for product imagery, editorial photography, and heritage collection media with licensing restrictions.

  • Rights and expiration dates are maintained in WoodWing metadata
  • xConnector filters assets based on approval and license status
  • Expired or restricted assets are blocked from downstream publication

Business value: Lowers legal and compliance risk and prevents unauthorized asset use.

7. Asset metadata enrichment and synchronization across business systems

Direction: Bi-directional

WoodWing can store rich asset metadata such as product codes, campaign IDs, collection references, and channel-specific tags. xConnector can synchronize this metadata with ERP, PIM, CMS, or archival systems so that all teams work from the same asset context.

  • Business systems provide master identifiers to WoodWing
  • WoodWing returns approved asset references and status updates
  • Metadata changes are kept aligned across platforms

Business value: Improves searchability, reduces duplicate asset creation, and supports more reliable cross-system reporting.

8. Legacy asset migration and consolidation into WoodWing

Direction: xConnector to WoodWing

If xConnector is used as an integration layer or migration utility, it can help consolidate image and video assets from older file shares, legacy DAMs, or departmental repositories into WoodWing. This is useful during digital transformation or platform rationalization initiatives.

  • Legacy assets are mapped to WoodWing metadata structures
  • xConnector migrates files, folders, and associated descriptions
  • Teams gain a single governed repository for ongoing asset management

Business value: Reduces fragmented storage, improves governance, and creates a cleaner foundation for future integrations.

How to integrate and automate WoodWing with xConnector using OneTeg?