OpenText DAM (OTMM) - Wrike Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and Wrike

OpenText DAM (OTMM) and Wrike complement each other well in organizations that manage high volumes of creative, product, and campaign assets. OTMM serves as the system of record for approved digital assets, while Wrike provides the work management layer for requests, reviews, approvals, and cross-functional execution. Integrating the two platforms helps teams reduce manual handoffs, improve asset governance, and accelerate delivery across marketing, product, and operations workflows.

1. Creative asset request intake from Wrike into OpenText DAM

Marketing or product teams can submit asset requests in Wrike using standardized request forms for new product images, campaign videos, event photography, or museum collection media. Once approved, the request can trigger asset creation or upload tasks in OpenText DAM, where the final files are stored, tagged, and governed.

• Data flow: Wrike to OpenText DAM
• Business value: Eliminates email-based requests and ensures every asset starts with the right brief, metadata, and approval path
• Typical users: Marketing operations, creative teams, product managers, content producers

2. DAM asset review and approval workflow managed in Wrike

When a new image, video, or campaign asset is uploaded to OpenText DAM, the integration can create a review task in Wrike for stakeholders such as brand, legal, product, or regional marketing teams. Reviewers can comment, approve, or request changes in Wrike while the approved version remains controlled in OTMM.

• Data flow: OpenText DAM to Wrike, with approval status returned to OpenText DAM
• Business value: Centralizes review cycles and reduces version confusion across teams
• Typical users: Creative directors, compliance reviewers, brand managers, legal teams

3. Approved asset publishing from OpenText DAM to Wrike project tasks

Once an asset is approved in OpenText DAM, the integration can automatically update the related Wrike project or task with the final file link, metadata, and approval status. This gives project teams immediate visibility into which assets are ready for use in campaigns, product launches, or channel distribution.

• Data flow: OpenText DAM to Wrike
• Business value: Improves project transparency and reduces time spent searching for final assets
• Typical users: Campaign managers, channel marketers, project coordinators

4. Campaign execution tracking tied to DAM asset status

Wrike can manage the full campaign timeline, including creative production, localization, and launch milestones, while OpenText DAM tracks the status of the actual assets. The integration can synchronize key asset milestones such as draft, in review, approved, localized, and published back into Wrike so project managers can monitor progress without leaving the work management environment.

• Data flow: Bi-directional
• Business value: Aligns project schedules with asset readiness and reduces launch delays
• Typical users: Marketing operations, project managers, regional marketing teams

5. Product content coordination for PIM and distribution workflows

For organizations managing product images and videos, OpenText DAM can store the approved media associated with product records, while Wrike coordinates the tasks required to prepare those assets for launch across ecommerce, retail, and distributor channels. Wrike tasks can reference the DAM asset ID, product SKU, or launch date, helping teams coordinate packaging, localization, and channel-specific deliverables.

• Data flow: Bi-directional, often with OpenText DAM as the asset source and Wrike as the workflow layer
• Business value: Speeds product launches and improves consistency across channels
• Typical users: Product marketing, ecommerce teams, channel operations, content operations

6. Event and broadcast production workflow management

For marketing events, corporate events, or broadcast production, Wrike can manage the production schedule, crew assignments, and deliverable deadlines, while OpenText DAM stores the raw footage, edited clips, and final masters. The integration can attach DAM links to Wrike tasks for editing, review, and distribution, ensuring teams always work from the correct media version.

• Data flow: OpenText DAM to Wrike, with task updates flowing back to OpenText DAM as needed
• Business value: Reduces media version errors and improves coordination across production teams
• Typical users: Video producers, event teams, broadcast operations, creative agencies

7. Heritage and museum collection media workflow

Museums and heritage organizations can use OpenText DAM to manage digital photos and videos of physical collections, while Wrike coordinates digitization projects, conservation reviews, metadata enrichment, and publication tasks. Each object or collection item can be linked to a Wrike task or project for tracking progress from capture through approval and public release.

• Data flow: Bi-directional
• Business value: Improves accountability for collection digitization programs and public content workflows
• Typical users: Curators, archivists, digitization teams, communications staff

8. Asset lifecycle reporting and operational visibility

Wrike dashboards can be used to monitor the operational status of asset-related work, such as how many campaign assets are in review, approved, localized, or delayed. OpenText DAM provides the authoritative asset metadata and usage status, while Wrike provides project-level reporting on workload, bottlenecks, and delivery performance. Together, they give leadership a clearer view of both asset governance and execution health.

• Data flow: Bi-directional
• Business value: Supports better planning, resource allocation, and SLA tracking for creative operations
• Typical users: Marketing leadership, operations managers, PMO teams

In summary, integrating OpenText DAM and Wrike creates a stronger end-to-end workflow from asset creation and governance to project execution and delivery. OTMM ensures assets are controlled, searchable, and approved, while Wrike ensures the work around those assets is visible, coordinated, and completed on time.