Wrike - OpenText Content Metadata Service Integration and Automation

Common Integration Use Cases Between Wrike and OpenText Content Metadata Service

Wrike and OpenText Content Metadata Service complement each other well in organizations that manage structured work alongside governed content. Wrike provides the operational layer for planning, assigning, and tracking work, while OpenText Content Metadata Service provides the metadata foundation needed to classify, standardize, and automate content handling across repositories. Together, they help teams connect project execution with content governance.

1. Standardized metadata capture for project deliverables

When a new project or creative request is created in Wrike, required metadata fields such as content type, business unit, region, retention class, campaign ID, or approval status can be pushed to OpenText Content Metadata Service. This ensures every deliverable is tagged consistently before it is stored or published.

• Direction: Wrike to OpenText Content Metadata Service
• Business value: Improves searchability, compliance, and downstream automation by eliminating inconsistent tagging
• Typical users: Marketing operations, creative teams, content governance teams

2. Metadata-driven intake and routing of content requests

Wrike request forms can collect structured information from business users, then send that data to OpenText Content Metadata Service to validate or enrich metadata models. Based on the metadata values, the request can be routed to the correct team, workflow, or repository classification.

• Direction: Wrike to OpenText Content Metadata Service
• Business value: Reduces manual triage and ensures requests enter the right workflow with the right classification from the start
• Typical users: Shared services teams, PMOs, content operations teams

3. Content approval workflow linked to metadata updates

As assets move through review and approval in Wrike, approval outcomes can trigger updates to metadata in OpenText Content Metadata Service. For example, once a legal review is completed, the content status metadata can be changed to approved, restricted, or ready for publication.

• Direction: Bi-directional
• Business value: Keeps content status aligned across work management and content systems, reducing the risk of publishing unapproved materials
• Typical users: Legal, compliance, brand, and content approval teams

4. Metadata synchronization for campaign and project reporting

Wrike project records can be enriched with metadata from OpenText Content Metadata Service, such as document category, campaign taxonomy, or content owner. This allows project dashboards and reports in Wrike to be filtered by standardized metadata, giving leaders better visibility into content production by region, product line, or business unit.

• Direction: OpenText Content Metadata Service to Wrike
• Business value: Enables more accurate reporting and portfolio analysis across content-heavy initiatives
• Typical users: Marketing leadership, project managers, operations analysts

5. Automated classification of creative assets during production

When creative assets are attached to Wrike tasks or proofing workflows, metadata rules from OpenText Content Metadata Service can classify the asset automatically based on project type, channel, audience, or geography. This supports consistent categorization before the asset is handed off to downstream systems.

• Direction: Wrike to OpenText Content Metadata Service
• Business value: Speeds up asset organization and reduces the risk of misfiled or poorly labeled content
• Typical users: Creative operations, digital asset management teams

6. Cross-system search and traceability for regulated content

Wrike task records can store references to metadata identifiers from OpenText Content Metadata Service, allowing teams to trace a deliverable back to its governed content record. This is especially useful in regulated industries where teams need to prove which version of a document was approved, when it was approved, and under what classification.

• Direction: Bi-directional
• Business value: Improves auditability and reduces time spent reconciling work records with content records
• Typical users: Compliance, quality assurance, regulated marketing teams

7. Reuse of metadata models across multiple Wrike workflows

OpenText Content Metadata Service can serve as the central source of truth for metadata models used across several Wrike workflows, such as product launches, customer communications, and knowledge publishing. When metadata definitions change, they can be updated centrally and reflected in Wrike request forms, custom fields, and automation rules.

• Direction: OpenText Content Metadata Service to Wrike
• Business value: Reduces duplicate configuration work and keeps metadata consistent across teams and projects
• Typical users: Enterprise architecture, content operations, workflow administrators

Overall, integrating Wrike with OpenText Content Metadata Service helps organizations connect execution with governance. Wrike manages the work, while OpenText ensures the content associated with that work is classified, searchable, and automation-ready.