Home | Connectors | WoodWing | WoodWing - OpenText Push Notifications for Cloud Messaging Integration and Automation

WoodWing - OpenText Push Notifications for Cloud Messaging Integration and Automation

Integrate WoodWing Digital Asset Management (DAM) and OpenText Push Notifications for Cloud Messaging Messaging / Communication 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 Push Notifications for Cloud Messaging

WoodWing manages rich digital assets such as product images, videos, marketing campaign files, museum collection media, and publishing content, while OpenText Push Notifications for Cloud Messaging delivers timely alerts to mobile and web users. Together, they can connect asset creation and approval workflows with real-time stakeholder communication, improving speed, visibility, and operational control.

1. New Asset Published Notification to Sales and Marketing Teams

Direction: WoodWing to OpenText Push Notifications for Cloud Messaging

When a new product image, campaign video, or publication asset is approved and published in WoodWing, OpenText can send a push notification to relevant users such as sales teams, regional marketers, or channel managers. This ensures teams are immediately aware that approved content is ready for use in campaigns, product listings, or distributor portals.

  • Reduces delays between asset approval and downstream usage
  • Improves coordination across marketing, sales, and content operations
  • Supports time-sensitive launches and campaign rollouts

2. Asset Review and Approval Alerts for Creative and Compliance Teams

Direction: WoodWing to OpenText Push Notifications for Cloud Messaging

When an asset is uploaded, updated, or moved into a review stage in WoodWing, OpenText can notify reviewers, legal approvers, or brand managers that action is required. This is especially useful for regulated industries, publishing workflows, and museum content validation where approvals must happen quickly and consistently.

  • Speeds up review cycles for images, videos, and layout files
  • Helps prevent bottlenecks in approval workflows
  • Improves governance and accountability for content sign-off

3. Expiring or Outdated Asset Replacement Notifications

Direction: WoodWing to OpenText Push Notifications for Cloud Messaging

WoodWing can trigger notifications when product images, campaign assets, or publication files are nearing expiration, have been superseded, or are marked for retirement. OpenText can alert content owners, ecommerce managers, or channel partners so they can replace outdated files before they are used in customer-facing channels.

  • Reduces risk of using obsolete or non-compliant assets
  • Supports brand consistency across channels
  • Helps maintain accurate product and campaign content

4. Distribution Channel Readiness Alerts for External Partners

Direction: WoodWing to OpenText Push Notifications for Cloud Messaging

When assets are prepared for syndication from WoodWing to external distribution channels, OpenText can notify partner users or internal channel coordinators that the content package is ready. This is useful for retailers, publishers, museum partners, and franchise networks that depend on timely asset availability.

  • Improves handoff between content teams and external recipients
  • Supports faster product launches and campaign activation
  • Reduces manual follow-up emails and status checks

5. Urgent Asset Change Notifications for Live Campaigns

Direction: WoodWing to OpenText Push Notifications for Cloud Messaging

If a live campaign image, event video, or product visual is updated in WoodWing due to a correction, compliance issue, or last-minute change, OpenText can immediately notify campaign managers and publishing teams. This helps teams react quickly and prevent the wrong asset from remaining active in web, mobile, or print workflows.

  • Supports rapid response to content corrections
  • Minimizes business risk during live campaigns
  • Improves operational control over distributed assets

6. Mobile Notification for Field Teams Accessing Asset Libraries

Direction: WoodWing to OpenText Push Notifications for Cloud Messaging

Field marketers, museum staff, photographers, and regional content coordinators using mobile apps can receive push notifications when new assets are available in WoodWing. This is useful for teams working away from desktop systems who need immediate access to approved images, videos, or publication files.

  • Improves access to assets for distributed teams
  • Increases adoption of approved content libraries
  • Supports faster execution in field and event environments

7. Workflow Exception and Missing Asset Alerts

Direction: WoodWing to OpenText Push Notifications for Cloud Messaging

When a required asset is missing, rejected, or fails validation in WoodWing, OpenText can send an alert to the responsible content owner or operations team. This is valuable in publishing, product content management, and museum digitization workflows where missing media can delay production or release schedules.

  • Helps teams resolve exceptions before deadlines are missed
  • Improves workflow transparency and accountability
  • Reduces manual monitoring of asset queues

8. User Action Notifications for Asset Comments and Collaboration

Direction: Bi-directional

When users comment on an asset, request changes, or complete a task in WoodWing, OpenText can notify the next responsible stakeholder through mobile or web push. In return, user responses or acknowledgments from the notification layer can be used to update workflow status in WoodWing. This creates a tighter collaboration loop for creative, editorial, and operations teams.

  • Improves responsiveness across distributed teams
  • Creates a more connected review and collaboration process
  • Supports real-time coordination without relying on email

How to integrate and automate WoodWing with OpenText Push Notifications for Cloud Messaging using OneTeg?