Home | Connectors | OpenText Core Content - Metadata | OpenText Core Content - Metadata - Papirfly Integration and Automation
OpenText Core Content - Metadata provides governed metadata structures, validation, and classification for enterprise content, while Papirfly is typically used to create, manage, and distribute brand assets and marketing materials. Together, they can improve brand consistency, content discoverability, and workflow control across creative, marketing, and content governance teams.
Flow: Papirfly to OpenText Core Content - Metadata
When marketing teams create new assets in Papirfly, required metadata such as campaign name, region, product line, language, usage rights, and expiry date can be pushed into OpenText Core Content - Metadata for validation and governance. This ensures every approved asset is classified consistently before it is stored or shared across the enterprise.
Flow: Papirfly to OpenText Core Content - Metadata
Once a campaign asset is approved in Papirfly, it can be transferred to OpenText Core Content with the correct metadata applied automatically. This creates a controlled enterprise record of final assets, making it easier for legal, compliance, and regional teams to find the latest approved version.
Flow: Bi-directional
Metadata captured in OpenText Core Content - Metadata can trigger workflow rules in Papirfly, such as routing assets for legal review when a specific product category or market is selected. In return, Papirfly can send approval status back to OpenText so only validated assets are retained or published.
Flow: Papirfly to OpenText Core Content - Metadata
By applying controlled vocabularies and standardized metadata from OpenText Core Content - Metadata to Papirfly assets, teams can search by campaign, audience, channel, geography, or product more effectively. This helps regional marketers and agencies quickly locate approved assets for reuse instead of recreating content.
Flow: Bi-directional
OpenText Core Content - Metadata can store structured fields for license terms, expiration dates, and permitted usage. Papirfly can use this metadata to prevent expired or restricted assets from being selected in new campaigns, while also updating OpenText when rights are extended or revised.
Flow: OpenText Core Content - Metadata to Papirfly
Global organizations can define metadata templates in OpenText Core Content - Metadata for language, market, region, and local regulatory requirements. Papirfly can then apply these standards when local teams adapt master assets, ensuring localized versions remain aligned with enterprise governance and are easy to track.
Flow: Bi-directional
Metadata from OpenText Core Content - Metadata combined with usage data from Papirfly can support reporting on which assets are used most often, which campaigns perform best, and where content governance gaps exist. Business teams can use this insight to optimize content production and retire underused assets.
Flow: Papirfly to OpenText Core Content - Metadata
When a campaign ends, Papirfly can send asset status updates to OpenText Core Content - Metadata so retention rules, archival tags, or disposal schedules can be applied automatically. This helps organizations manage content lifecycle policies without relying on manual cleanup.