Ziflow - OpenText Core Digital Asset Management Integration and Automation

Common Integration Use Cases Between Ziflow and OpenText Core Digital Asset Management

Below are practical integration scenarios where Ziflow and OpenText Core Digital Asset Management work together to streamline creative review, asset governance, and content delivery across enterprise teams.

1. Send approved creative assets from Ziflow to OpenText Core Digital Asset Management

Data flow: Ziflow to OpenText Core Digital Asset Management

When a creative proof reaches final approval in Ziflow, the approved file, version, and approval status can be automatically pushed into OpenText Core Digital Asset Management for long-term storage, tagging, and distribution.

• Eliminates manual downloading and re-uploading of final assets
• Ensures only approved versions are published to the DAM
• Supports centralized asset governance and reuse across teams

2. Launch Ziflow review workflows from assets stored in OpenText Core Digital Asset Management

Data flow: OpenText Core Digital Asset Management to Ziflow

Marketing or creative teams can initiate a proofing cycle directly from a selected asset in OpenText Core Digital Asset Management, sending it to Ziflow for review and approval by stakeholders.

• Speeds up review initiation without duplicating files
• Reduces the risk of reviewing outdated or incorrect versions
• Improves collaboration between DAM users and creative approvers

3. Sync approval status back to OpenText Core Digital Asset Management for asset governance

Data flow: Ziflow to OpenText Core Digital Asset Management

Once a proof is approved, rejected, or requires changes in Ziflow, that status can be written back to OpenText Core Digital Asset Management so asset managers can see the current lifecycle state of each file.

• Provides visibility into which assets are approved for use
• Helps prevent premature publishing of unapproved content
• Supports compliance and audit readiness with clear approval records

4. Create a closed-loop version control process for creative assets

Data flow: Bi-directional

When a revised asset is uploaded to OpenText Core Digital Asset Management, it can be sent to Ziflow for a new review cycle. After approval, the final version and approval metadata can be returned to OpenText Core Digital Asset Management as the authoritative record.

• Maintains a clear chain of versions and approvals
• Reduces confusion over which file is final
• Improves control over regulated or high-volume content production

5. Automate stakeholder notifications when approved assets are ready in the DAM

Data flow: Ziflow to OpenText Core Digital Asset Management, then OpenText Core Digital Asset Management to downstream users

After approval in Ziflow, OpenText Core Digital Asset Management can trigger notifications to brand, sales, regional marketing, or agency users that a new approved asset is available for use.

• Accelerates time to market for campaigns and launches
• Reduces dependency on manual email follow-ups
• Improves adoption of approved, on-brand content

6. Pass metadata and approval attributes from Ziflow into OpenText Core Digital Asset Management

Data flow: Ziflow to OpenText Core Digital Asset Management

Approval details such as reviewer names, approval date, campaign name, asset status, and proof comments can be transferred into OpenText Core Digital Asset Management to enrich asset metadata.

• Improves searchability and reporting in the DAM
• Creates a richer audit trail for content governance
• Helps teams identify approved assets by campaign, region, or channel

7. Support enterprise content operations with automated handoff between creative review and asset management

Data flow: Bi-directional

Creative teams can manage review and markup in Ziflow while asset managers maintain master records, taxonomy, and distribution control in OpenText Core Digital Asset Management. Integration ensures assets move smoothly between review and storage stages.

• Aligns creative production with enterprise DAM governance
• Reduces operational bottlenecks between teams
• Improves consistency across global content operations

8. Improve compliance for regulated content approvals

Data flow: Bi-directional

For regulated industries such as healthcare, financial services, or consumer goods, Ziflow can capture formal approvals and comments, while OpenText Core Digital Asset Management stores the approved asset and associated compliance metadata for retention and retrieval.

• Creates a defensible approval record
• Supports internal and external audits
• Helps ensure only compliant content is distributed

In combination, Ziflow and OpenText Core Digital Asset Management create a more controlled and efficient content lifecycle, from creative review through approved asset storage and reuse.