Adobe Workfront - OpenText TeamSite - LiveSite Content Services Integration and Automation

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

1. Campaign Brief to Website Content Delivery Workflow

Direction: Adobe Workfront → OpenText TeamSite - LiveSite Content Services

Marketing teams can create campaign briefs, timelines, and approval workflows in Adobe Workfront, then push approved content requirements to OpenText TeamSite for web publishing. This ensures website updates, landing pages, and promotional banners are aligned with campaign plans and launch dates.

• Workfront manages intake, creative review, and launch approvals
• TeamSite receives finalized content requirements for page updates
• Reduces manual handoffs between marketing operations and web publishing teams

Business value: Faster campaign launches, fewer content errors, and better coordination between creative and digital experience teams.

2. Creative Asset Approval Before Web Publishing

Direction: Adobe Workfront → OpenText TeamSite - LiveSite Content Services

Creative assets such as banners, hero images, and promotional graphics can be reviewed and approved in Workfront before being published through TeamSite. Once approved, asset metadata, usage rights, and version status can be passed to the content delivery platform for deployment on customer-facing sites.

• Workfront handles proofing, comments, and final sign-off
• TeamSite publishes only approved assets to live digital properties
• Supports brand governance and reduces risk of unapproved content going live

Business value: Stronger brand control, fewer compliance issues, and more reliable publishing operations.

3. Personalized Content Requests from Digital Experience Teams

Direction: OpenText TeamSite - LiveSite Content Services → Adobe Workfront

When web teams identify a need for new personalized content, landing page variants, or localized messaging, TeamSite can create structured requests in Workfront for creative production. Workfront then routes the request to the right designers, copywriters, and approvers.

• TeamSite triggers content creation requests based on site needs
• Workfront manages production tasks and approval routing
• Improves responsiveness to customer behavior and campaign performance data

Business value: Faster turnaround for content changes and better alignment between digital experience and creative operations.

4. Launch Readiness Tracking for New Web Experiences

Direction: Bi-directional

For product launches, events, or seasonal campaigns, Workfront can track all creative and content production tasks while TeamSite tracks readiness of the website or portal content. Status updates can flow between both systems so stakeholders have a single view of launch readiness.

• Workfront tracks task completion, approvals, and dependencies
• TeamSite reflects content staging and publishing readiness
• Supports launch governance across marketing, web, and business teams

Business value: Better launch coordination, fewer missed dependencies, and improved visibility for leadership.

5. Content Localization and Regional Site Updates

Direction: Adobe Workfront → OpenText TeamSite - LiveSite Content Services

Global marketing teams can manage localization requests in Workfront for translated copy, region-specific imagery, and legal review. Once approved, TeamSite can receive the localized content package and publish it to the appropriate regional site or portal.

• Workfront manages translation tasks and regional approvals
• TeamSite deploys localized content to the correct site variants
• Helps maintain consistency across global digital properties

Business value: More efficient multilingual publishing and reduced risk of inconsistent regional messaging.

6. Content Change Requests from Customer-Facing Portals

Direction: OpenText TeamSite - LiveSite Content Services → Adobe Workfront

Business users or web editors working in TeamSite can submit content change requests into Workfront when they need new creative, updated copy, or compliance review. This creates a controlled workflow for changes that require marketing, legal, or brand approval.

• TeamSite captures change requests from digital content operations
• Workfront routes work to the correct teams for execution
• Ensures traceability for content changes on live sites

Business value: Better governance, fewer ad hoc requests, and improved accountability for website updates.

7. Asset and Content Status Synchronization for Publishing Teams

Direction: Bi-directional

Workfront can send asset status updates such as in review, approved, or expired to TeamSite, while TeamSite can return publishing status such as staged, scheduled, or live. This gives marketing and web teams a shared operational view of what is ready for deployment and what still needs work.

• Synchronizes approval and publishing states across systems
• Reduces duplicate tracking in spreadsheets or email threads
• Improves operational transparency for content operations teams

Business value: Fewer publishing delays, better status visibility, and more efficient cross-team coordination.

8. Post-Launch Content Performance Feedback Loop

Direction: OpenText TeamSite - LiveSite Content Services → Adobe Workfront

After content is published in TeamSite, performance insights such as page engagement, conversion results, or content refresh needs can be sent back to Workfront as new work items. Marketing teams can then prioritize updates, redesigns, or A/B test variants based on live site performance.

• TeamSite provides content performance or refresh triggers
• Workfront converts insights into actionable production tasks
• Supports continuous improvement of digital experiences

Business value: More data-driven content operations and faster response to underperforming web content.