Home | Connectors | WoodWing | WoodWing - OpenText TeamSite Authoring Services Integration and Automation

WoodWing - OpenText TeamSite Authoring Services Integration and Automation

Integrate WoodWing Digital Asset Management (DAM) and OpenText TeamSite Authoring Services Content Management System (CMS) / eCommerce 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 OpenText TeamSite Authoring Services

WoodWing is well suited for managing rich media and digital assets such as product images, campaign visuals, museum collection media, and publishing files. OpenText TeamSite Authoring Services is designed for structured web content creation, collaboration, and approval workflows. Together, they can support a controlled flow of approved assets from creative and content operations into web publishing environments.

  • Approved marketing assets published to website pages
    WoodWing can serve as the central repository for final campaign images, banners, and event photography, while OpenText TeamSite pulls approved assets into web pages and landing pages. This reduces manual file handling, ensures only brand-approved media is used online, and speeds up campaign launches.
  • Product image syndication from asset management to web content
    For organizations managing product catalogs, WoodWing can store master product images and variants, then publish selected renditions to OpenText TeamSite for use on product detail pages, category pages, and promotional content. This creates a controlled handoff from asset management to web publishing and helps maintain consistency across channels.
  • Editorial publishing workflow for books and digital publications
    WoodWing can manage book assets, photography, InDesign layouts, and epub-related media, while OpenText TeamSite can host companion web content such as author pages, chapter previews, launch announcements, and downloadable excerpts. This supports coordinated publishing across print and digital channels with shared approvals and asset reuse.
  • Museum and heritage content publishing
    Museums and heritage organizations can store collection images and video in WoodWing, then use OpenText TeamSite to publish exhibit pages, collection stories, and educational content. Curators and web editors can work from approved media assets, improving governance and reducing the risk of outdated or unapproved imagery appearing on public sites.
  • Campaign content assembly for marketing teams
    Marketing teams can manage campaign visuals, event photography, and video clips in WoodWing, while OpenText TeamSite authors build campaign microsites and promotional pages using those assets. Integration supports faster content assembly, consistent brand usage, and easier reuse of assets across multiple campaigns and regions.
  • Bi-directional approval and status synchronization
    When a web content item in OpenText TeamSite requires a new image or video, the request can be sent to WoodWing for asset selection or approval. Once the asset is approved or updated in WoodWing, the status can be reflected back in TeamSite so authors know when content is ready for publication. This improves workflow visibility and reduces content bottlenecks.
  • Centralized asset governance for multi-channel publishing
    WoodWing can act as the system of record for approved media, while OpenText TeamSite consumes those assets for web publishing. Metadata such as usage rights, expiration dates, campaign tags, and product associations can be synchronized so web teams only use compliant assets. This lowers legal and brand risk and supports auditability.

These integrations are most valuable when WoodWing remains the authoritative source for rich media and OpenText TeamSite manages the web content experience. The result is a cleaner workflow between creative, editorial, and digital teams, with fewer duplicate assets, faster approvals, and more consistent publishing across channels.

How to integrate and automate WoodWing with OpenText TeamSite Authoring Services using OneTeg?