Wrike - OpenText TeamSite - LiveSite Content Services Integration and Automation

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

1. Marketing campaign intake to web content delivery

Flow: Wrike ? OpenText TeamSite - LiveSite Content Services

Marketing teams can use Wrike as the intake and planning layer for website and campaign content requests. Once a campaign brief, landing page request, or content asset is approved in Wrike, the integration can create or update the corresponding content item in TeamSite for web publishing. This reduces manual handoffs between marketing operations, content teams, and web publishers.

• Wrike captures campaign requirements, deadlines, and approvals
• Approved content is pushed to TeamSite for page creation or update
• Web teams receive structured tasks with due dates and asset links
• Improves launch speed and reduces missed publishing steps

2. Content approval workflow for digital experience assets

Flow: Bi-directional

Wrike can manage review and approval tasks for web copy, banners, and page modules while TeamSite stores and renders the final approved content. Content editors and approvers work in Wrike for review cycles, and once approved, the status is synchronized back to TeamSite so only approved assets are published. This creates a controlled governance process for customer-facing content.

• Wrike manages review tasks, proofing, and stakeholder sign-off
• TeamSite receives approval status before publishing
• Rejected content is routed back to writers or designers in Wrike
• Supports compliance and brand consistency across digital channels

3. Website localization and regional content coordination

Flow: Wrike ? OpenText TeamSite - LiveSite Content Services

Global organizations can use Wrike to coordinate localization work for regional websites, including translation, legal review, and market-specific edits. Once regional content is approved in Wrike, the localized version can be sent to TeamSite for rendering on the appropriate site or portal. This helps regional teams launch content in sync with corporate campaigns.

• Wrike tracks translation tasks and regional approvals
• Localized content is delivered to TeamSite by market or language
• Regional launch dates are aligned with global campaign timelines
• Reduces delays caused by email-based content coordination

4. Web content change requests from business teams

Flow: OpenText TeamSite - LiveSite Content Services ? Wrike

When business users identify a need to update a web page, portal message, or personalized content block, TeamSite can trigger a Wrike task for the responsible team. This gives marketing, product, or communications teams a structured workflow for triage, assignment, and completion instead of relying on informal requests.

• Content issues or update requests are logged from TeamSite into Wrike
• Wrike assigns the task to the correct owner with SLA and priority
• Teams track progress, dependencies, and approvals in one place
• Improves accountability for web content maintenance

5. Product launch coordination between project teams and web publishing

Flow: Bi-directional

For product launches, Wrike can manage the cross-functional project plan across product, marketing, legal, and web teams, while TeamSite handles the live delivery of launch pages and supporting content. Milestones in Wrike can trigger content readiness checks in TeamSite, ensuring that the website is updated only when launch assets are complete and approved.

• Wrike manages launch milestones, dependencies, and owners
• TeamSite publishes launch pages, FAQs, and customer messaging
• Launch readiness can be monitored across both systems
• Reduces risk of publishing incomplete or unapproved content

6. Personalized content request management for digital experience teams

Flow: Wrike ? OpenText TeamSite - LiveSite Content Services

Digital experience teams often need to create personalized content variants for different audiences, campaigns, or customer segments. Wrike can be used to manage the request, review, and production workflow for these variants, then pass the approved content to TeamSite for real-time rendering and personalization. This is especially useful for enterprise portals and customer-facing websites.

• Wrike tracks audience-specific content requests and approvals
• TeamSite receives content variants for dynamic delivery
• Supports coordinated work between strategy, content, and web operations
• Improves speed of personalized digital experience updates

7. Governance and audit trail for regulated web content

Flow: Bi-directional

Organizations in regulated industries can use Wrike to manage the full content governance process, including drafting, legal review, compliance approval, and publication readiness. TeamSite then serves as the controlled delivery platform for approved content. Synchronizing task status and approval metadata between the systems creates a clear audit trail for who approved what and when.

• Wrike manages compliance review tasks and approval checkpoints
• TeamSite publishes only content that has passed governance steps
• Approval history is retained for audit and reporting purposes
• Supports controlled publishing for financial services, healthcare, and public sector teams