Home | Connectors | Frontify | Frontify - OpenText Core Digital Asset Management Integration and Automation

Frontify - OpenText Core Digital Asset Management Integration and Automation

Integrate Frontify Digital Asset Management (DAM) and OpenText Core Digital Asset Management Cloud Storage 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 Frontify and OpenText Core Digital Asset Management

1. Publish approved brand assets from OpenText Core DAM to Frontify

Direction: OpenText Core Digital Asset Management ? Frontify

Marketing and design teams can push approved logos, campaign images, product photography, and video files from OpenText Core DAM into Frontify as the brand-ready source for internal teams and agencies. This ensures Frontify always reflects the latest approved assets while OpenText remains the system of record for master files and metadata.

  • Reduces duplicate asset storage and version confusion
  • Improves brand consistency across distributed teams
  • Speeds up asset access for campaign execution

2. Sync brand guidelines and usage rules with asset metadata

Direction: Bi-directional

Frontify can provide brand governance context such as usage rules, campaign tags, regional restrictions, and approved channels, while OpenText Core DAM can supply technical metadata, rights information, and asset status. Together, they create a more complete asset record that helps teams understand not just what an asset is, but how it can be used.

  • Supports compliance with licensing and usage rights
  • Improves search and filtering by business context
  • Helps regional teams apply the correct brand rules

3. Route final approved creative from Frontify to OpenText Core DAM for enterprise storage

Direction: Frontify ? OpenText Core Digital Asset Management

When creative work is reviewed and approved in Frontify, final versions can be transferred to OpenText Core DAM for long-term storage, governance, and distribution. This is useful for organizations that use Frontify as the collaboration and brand review layer, but rely on OpenText as the enterprise DAM repository.

  • Creates a controlled handoff from review to archive
  • Preserves approved versions for future reuse
  • Supports auditability and asset lifecycle management

4. Keep campaign asset libraries aligned across both platforms

Direction: Bi-directional

For large campaigns, assets can be synchronized between Frontify and OpenText Core DAM so that both marketing operations and brand teams work from the same approved library. Updates to asset status, version, or expiration in one system can trigger updates in the other, reducing manual reconciliation.

  • Prevents teams from working on outdated files
  • Improves campaign launch coordination
  • Reduces manual asset administration

5. Enrich Frontify with OpenText DAM asset renditions and derivatives

Direction: OpenText Core Digital Asset Management ? Frontify

OpenText Core DAM can generate and supply renditions such as web-optimized images, thumbnails, or region-specific formats to Frontify. Frontify users then access the right derivative for brand portals, presentations, and internal communications without needing to manually resize or reformat files.

  • Accelerates content reuse across channels
  • Ensures consistent output formats for teams
  • Reduces design workload for routine adaptations

6. Push brand-approved assets from Frontify into downstream publishing workflows

Direction: Frontify ? OpenText Core Digital Asset Management

Once assets are approved in Frontify, they can be sent to OpenText Core DAM for use by downstream systems such as CMS, e-commerce platforms, or regional content hubs. This creates a controlled publishing pipeline where only brand-approved content is made available for broader enterprise use.

  • Improves governance before content distribution
  • Supports omnichannel publishing workflows
  • Minimizes risk of unapproved asset usage

7. Centralize asset lifecycle status and expiration management

Direction: Bi-directional

OpenText Core DAM can manage asset lifecycle states such as draft, approved, archived, or expired, while Frontify can reflect those states in brand portals and guideline pages. When an asset expires or is withdrawn in OpenText, Frontify can automatically hide or flag it to prevent continued use.

  • Reduces legal and compliance exposure
  • Keeps brand portals current and trustworthy
  • Helps teams avoid using outdated or expired content

8. Support agency and regional team collaboration with controlled access

Direction: OpenText Core Digital Asset Management ? Frontify

OpenText Core DAM can serve as the secure master repository for sensitive or high-value assets, while Frontify provides a more accessible brand experience for agencies, sales teams, and regional marketers. Integration allows controlled exposure of approved assets and related brand guidance without opening access to the full DAM repository.

  • Balances governance with ease of access
  • Improves self-service for distributed teams
  • Reduces dependency on central marketing operations

How to integrate and automate Frontify with OpenText Core Digital Asset Management using OneTeg?