Home | Connectors | OpenText TeamSite Authoring Services | OpenText TeamSite Authoring Services - Papirfly Integration and Automation
OpenText TeamSite Authoring Services and Papirfly can complement each other well in enterprise marketing and digital content operations. TeamSite is typically used to manage structured web content, editorial workflows, and publishing approvals, while Papirfly is often used to centralize brand assets, templates, and localized marketing materials. Together, they can improve content consistency, speed up campaign execution, and reduce manual handoffs between web, brand, and regional teams.
Direction: Papirfly to OpenText TeamSite Authoring Services
Marketing teams can store approved logos, banners, product images, and campaign visuals in Papirfly and make them available to content authors in TeamSite. When authors build or update web pages, they can pull only approved brand assets from Papirfly instead of using local files or outdated shared drives.
Direction: Bi-directional
When a campaign asset or template is approved in Papirfly, metadata or status updates can be sent to TeamSite to notify web editors that content is ready for publishing. TeamSite can then use that approval status to move related pages through its workflow faster.
Direction: Papirfly to OpenText TeamSite Authoring Services
Global marketing teams can create master campaign assets in Papirfly and distribute localized versions to regional teams. Those localized assets can then be referenced in TeamSite for country-specific website pages, landing pages, or microsites.
Direction: OpenText TeamSite Authoring Services to Papirfly
TeamSite can manage the editorial workflow for web pages, while Papirfly can handle brand review and approval for associated assets. Content authors submit page drafts in TeamSite, and any new or updated creative elements are routed to Papirfly for brand validation before final publication.
Direction: Bi-directional
For major product launches or seasonal campaigns, Papirfly can serve as the source of approved campaign kits, including visuals, banners, and templates. TeamSite can consume those assets to build landing pages and campaign microsites, while publishing status or page usage data can be sent back to Papirfly for campaign tracking and reuse planning.
Direction: Papirfly to OpenText TeamSite Authoring Services
Asset metadata such as campaign name, product line, region, language, usage rights, and expiration date can be synchronized from Papirfly into TeamSite. This allows web authors to search and filter approved assets more effectively when building content.
Direction: OpenText TeamSite Authoring Services to Papirfly
Approved web content snippets, headlines, product descriptions, and campaign messaging from TeamSite can be pushed into Papirfly for reuse in brochures, social templates, email headers, and other branded materials. This helps maintain message consistency across channels.
Direction: Papirfly to OpenText TeamSite Authoring Services
When an asset in Papirfly reaches its expiration date or is replaced with a new version, TeamSite can receive an update to flag pages using the outdated asset. Content owners can then review and replace the asset before it is published or remains live on the website.