OpenText DAM (OTMM) - Asana Integration and Automation

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

OpenText DAM (OTMM) is used to store, manage, and distribute rich media assets such as product images, campaign creative, museum collections, and broadcast video. Asana is used to plan work, assign tasks, track approvals, and coordinate cross-functional delivery. Together, they help teams connect asset production and governance with structured project execution.

1. Campaign Asset Request and Production Workflow

Direction: Asana to OpenText DAM (OTMM) and bi-directional status updates

Marketing teams can create an Asana task or project for a new campaign asset request, such as product photography, social media creative, or event video. Once the request is approved, the task can trigger asset creation and upload into OTMM. Asset metadata, version status, and approval completion can then be synchronized back to Asana so project managers can track progress without manually checking the DAM.

• Reduces email-based handoffs between marketing, creative, and DAM teams
• Improves visibility into asset production milestones
• Supports faster campaign launch readiness

2. Product Image Review and Approval Management

Direction: OpenText DAM (OTMM) to Asana

When new product images are uploaded to OTMM, an Asana task can be automatically created for merchandising, brand, legal, or eCommerce review. The task can include asset links, product identifiers, and required approval steps. Once reviewers complete their work in Asana, the approved status can be returned to OTMM for controlled distribution to PIM, commerce, or channel teams.

• Speeds up product content approval cycles
• Ensures the right stakeholders review the right assets
• Creates an auditable workflow for regulated or high-volume product launches

3. Museum Collection Digitization Project Tracking

Direction: Asana to OpenText DAM (OTMM)

Museums and heritage organizations can use Asana to manage digitization projects for photos, artifacts, and archival video. Each digitization task can represent a collection item or batch, with deadlines, assigned conservators, and dependencies. Once digitized, the final media files and descriptive metadata can be uploaded to OTMM for long-term preservation and controlled access.

• Improves coordination across curators, archivists, and digital teams
• Provides a structured way to track large-scale digitization programs
• Separates project execution from asset preservation and access management

4. Broadcast and Video Production Coordination

Direction: Bi-directional

For broadcast and on-demand video workflows, Asana can manage production tasks such as scripting, editing, captioning, and compliance review, while OTMM stores the source footage, final masters, and derivative versions. Asana tasks can reference OTMM assets, and OTMM can update Asana when a new cut, approved master, or localized version is available. This keeps production teams aligned across multiple review cycles.

• Supports complex video production timelines
• Improves version control and review coordination
• Helps teams manage localized or channel-specific deliverables

5. Event Media Intake and Post-Event Content Workflow

Direction: OpenText DAM (OTMM) to Asana

After a marketing or company event, uploaded photos and videos in OTMM can automatically generate Asana tasks for content selection, editing, social publishing, and internal communications. Each task can be assigned to the relevant team with due dates and asset links. This creates a repeatable process for turning raw event media into approved content quickly.

• Accelerates post-event content repurposing
• Improves accountability for content owners and editors
• Helps teams reuse event media across multiple channels

6. Asset Expiration, Renewal, and Reuse Planning

Direction: OpenText DAM (OTMM) to Asana

When assets in OTMM approach expiration, such as licensed photography, seasonal campaign creative, or time-sensitive promotional video, Asana tasks can be created for renewal, replacement, or retirement. Teams can assign legal, procurement, brand, or channel owners to take action before assets become non-compliant or unusable.

• Reduces risk of using expired or unauthorized media
• Supports proactive content governance
• Helps maintain continuity across campaigns and channels

7. Cross-Functional Launch Readiness Tracking

Direction: Bi-directional

For product launches or major campaigns, Asana can manage the overall launch plan while OTMM serves as the source of approved images and videos. As assets move through review and approval in OTMM, their status can update launch tasks in Asana. Conversely, Asana can trigger asset requests when launch dependencies are identified, such as missing hero images, retailer-specific formats, or localized video cuts.

• Aligns creative delivery with launch milestones
• Prevents launch delays caused by missing media assets
• Improves coordination between marketing, product, and operations teams

These integration patterns help organizations connect asset management with execution management, reducing manual coordination and improving the speed, quality, and governance of media-driven business processes.