OpenText TeamSite - LiveSite Content Services - Ziflow Integration and Automation

Common Integration Use Cases Between OpenText TeamSite - LiveSite Content Services and Ziflow

1. Creative asset approval before publishing to digital channels

Data flow: Ziflow → OpenText TeamSite - LiveSite Content Services

Marketing and content teams can route banners, hero images, landing page copy, and campaign visuals through Ziflow for structured review and approval before they are published in TeamSite. Once approved, the final asset or content package can be pushed into TeamSite for rendering on websites and portals.

Business value: Reduces publishing errors, shortens approval cycles, and ensures only approved content reaches customer-facing channels.

2. Personalized campaign content review and sign-off

Data flow: OpenText TeamSite - LiveSite Content Services → Ziflow

When digital teams create personalized page variants or audience-specific content in TeamSite, those variants can be sent to Ziflow for review by brand, legal, and regional stakeholders. Reviewers can validate messaging, layout, and compliance for each audience segment before activation.

Business value: Improves governance for personalized experiences and reduces the risk of regionally incorrect or non-compliant content going live.

3. Automated approval workflow for campaign launch packages

Data flow: Bi-directional

TeamSite can trigger a Ziflow proof when a new campaign page, microsite, or content bundle is ready for review. Ziflow then returns approval status to TeamSite, allowing content to move from draft to scheduled or published states automatically. This supports coordinated launch workflows across content, creative, and web operations teams.

Business value: Eliminates manual follow-up, improves launch coordination, and creates a clear audit trail for approvals.

4. Legal and compliance review for regulated content

Data flow: OpenText TeamSite - LiveSite Content Services → Ziflow

For regulated industries such as financial services, healthcare, or insurance, TeamSite-managed content can be routed into Ziflow for mandatory legal, compliance, and disclosure review. Approved content is then released back to TeamSite for publication, while rejected content is returned with comments for revision.

Business value: Supports controlled publishing, reduces compliance risk, and ensures review evidence is retained in a centralized proofing system.

5. Content update requests from proofing feedback

Data flow: Ziflow → OpenText TeamSite - LiveSite Content Services

Reviewers in Ziflow often identify copy changes, image replacements, or layout adjustments during proofing. Those comments can be converted into actionable update requests for TeamSite content authors or web editors, helping them revise the source content and republish faster.

Business value: Speeds up revision cycles, reduces miscommunication between creative and web teams, and keeps content changes aligned to reviewer feedback.

6. Localization and regional content approval

Data flow: OpenText TeamSite - LiveSite Content Services → Ziflow

TeamSite can generate localized page versions or translated content variants and send them to Ziflow for review by regional marketing teams, translators, and country managers. This is especially useful for validating language accuracy, local offers, imagery, and legal disclaimers before regional publication.

Business value: Improves localization quality, reduces market-specific publishing errors, and accelerates global content rollout.

7. Audit-ready content governance for enterprise publishing

Data flow: Bi-directional

TeamSite manages the content lifecycle and publishing state, while Ziflow stores proofing history, reviewer comments, and approval decisions. Integrating the two creates a complete governance record from content creation through final publication, which is valuable for audits, internal controls, and post-launch traceability.

Business value: Strengthens accountability, simplifies audit preparation, and provides visibility into who approved what and when.