OpenText TeamSite Authoring Services - Ziflow Integration and Automation

Common Integration Use Cases Between OpenText TeamSite Authoring Services and Ziflow

OpenText TeamSite Authoring Services and Ziflow complement each other well in enterprise content operations. TeamSite manages structured web content creation, governance, and publishing workflows, while Ziflow adds a dedicated proofing layer for creative review, annotation, and approval. Together, they help marketing, digital, and creative teams reduce review cycles, improve content quality, and maintain stronger control over web publishing.

1. Web Content Drafts Sent from TeamSite to Ziflow for Creative Review

Data flow: OpenText TeamSite Authoring Services to Ziflow

When a marketing or web content author completes a page draft in TeamSite, the content can be automatically sent to Ziflow as a proof for review by brand, legal, design, or regional stakeholders. This is especially useful for homepage updates, campaign landing pages, and product content that require multiple approvals before publishing.

• Reduces manual file exports and email-based review requests
• Keeps creative feedback centralized in one proofing workspace
• Speeds up approval cycles for web publishing teams

2. Approved Proofs Returned from Ziflow to TeamSite for Final Publishing

Data flow: Ziflow to OpenText TeamSite Authoring Services

Once a proof is approved in Ziflow, the approval status and final annotated version can be pushed back to TeamSite so content authors can finalize and publish the approved web page or content asset. This creates a controlled handoff from review to production.

• Ensures only approved content moves into the publishing workflow
• Provides a clear audit trail of review and signoff
• Minimizes the risk of publishing outdated or unapproved content

3. Structured Approval Routing for Regulated or High-Risk Content

Data flow: Bi-directional

For regulated industries such as financial services, healthcare, or pharmaceuticals, TeamSite can initiate the content workflow and Ziflow can manage detailed proofing and signoff from compliance, legal, and subject matter experts. Approval status can then sync back to TeamSite to enforce governance before publication.

• Supports multi-step review for sensitive content
• Improves compliance oversight and documentation
• Helps teams enforce mandatory approvals before go-live

4. Campaign Page and Banner Review with Visual Markup in Ziflow

Data flow: OpenText TeamSite Authoring Services to Ziflow

Marketing teams often need visual review of page layouts, hero banners, promotional modules, and call-to-action placements. TeamSite can send page renders or creative previews to Ziflow, where reviewers can annotate directly on the visual proof instead of leaving comments in separate documents or chat threads.

• Improves clarity of feedback on layout, copy, and branding issues
• Reduces rework caused by ambiguous comments
• Supports faster iteration on time-sensitive campaign assets

5. Localization and Regional Market Review Workflow

Data flow: Bi-directional

Global organizations can use TeamSite to manage localized web content versions and send each regional variant to Ziflow for market-specific review. Local reviewers can confirm language, imagery, legal disclaimers, and cultural fit in Ziflow, then approved versions can be returned to TeamSite for regional publishing.

• Supports efficient multilingual and multi-market content operations
• Improves consistency while allowing local market validation
• Reduces delays caused by scattered regional feedback

6. Automated Review Triggers for Content Changes and Revisions

Data flow: OpenText TeamSite Authoring Services to Ziflow

When a page or content block is edited in TeamSite after an initial approval, the integration can automatically create a new proof in Ziflow for re-review. This is valuable for last-minute copy changes, pricing updates, legal wording changes, or refreshed imagery that require renewed approval.

• Prevents unreviewed edits from bypassing governance
• Ensures revision control across content versions
• Helps teams manage fast-moving content without losing oversight

7. Approval Status Sync for Workflow Visibility Across Teams

Data flow: Bi-directional

TeamSite users need visibility into whether content is still under review, approved, or rejected in Ziflow. Syncing proof status back into TeamSite gives authors, editors, and publishing managers a single view of content readiness without switching systems.

• Improves transparency across marketing, creative, and web operations
• Reduces follow-up emails and status meetings
• Helps publishing teams prioritize ready-to-launch content

8. Audit and Governance Reporting for Content Approvals

Data flow: Ziflow to OpenText TeamSite Authoring Services

Approval metadata from Ziflow, such as reviewer names, timestamps, comments, and final decision status, can be stored or referenced in TeamSite to support governance reporting and audit requirements. This is useful for organizations that need proof of review history for internal controls or external audits.

• Creates a documented approval trail for published content
• Supports compliance and operational governance
• Helps teams demonstrate who approved what and when