FTP - OpenText TeamSite - LiveSite Content Services Integration and Automation

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

1. Automated media and asset publishing to digital experiences

Data flow: FTP to OpenText TeamSite - LiveSite Content Services

Marketing, creative, or production teams can drop approved images, banners, PDFs, and video files into an FTP or SFTP location. OpenText TeamSite - LiveSite Content Services can ingest these assets and publish them to websites, portals, or campaign landing pages. This supports scheduled content refreshes without manual uploads by web teams.

• Reduces delays between asset approval and site publication
• Supports large file transfers that are common in media-rich campaigns
• Improves coordination between creative, marketing, and web operations teams

2. Bulk content updates for product or catalog-driven websites

Data flow: FTP to OpenText TeamSite - LiveSite Content Services

Retailers, manufacturers, and distributors often receive bulk product data, pricing files, or catalog updates from upstream systems via FTP. OpenText TeamSite - LiveSite Content Services can use these files to update product detail pages, category pages, and promotional content on customer-facing sites. This is especially useful for scheduled batch updates across large inventories.

• Speeds up publishing of seasonal or price-sensitive content
• Minimizes manual re-entry of product information
• Helps maintain consistency between source data and published web content

3. Partner content exchange for co-branded portals

Data flow: FTP to OpenText TeamSite - LiveSite Content Services

External agencies, distributors, or brand partners can deliver approved co-branded assets through FTP for ingestion into OpenText TeamSite - LiveSite Content Services. The platform can then render the content in partner portals, campaign microsites, or localized experience pages. This is useful when partners require file-based delivery rather than API-based integration.

• Supports structured partner onboarding and content exchange
• Enables controlled publishing of externally supplied materials
• Reduces dependency on ad hoc email-based asset sharing

4. Scheduled localization and regional content deployment

Data flow: FTP to OpenText TeamSite - LiveSite Content Services

Regional teams can upload translated copy, localized images, and market-specific documents to FTP folders by geography or business unit. OpenText TeamSite - LiveSite Content Services can then distribute the content to the correct regional pages or portals. This supports multi-market publishing with clear operational ownership.

• Improves speed of multilingual content rollout
• Supports regional governance and approval workflows
• Helps ensure the right content appears in the right market

5. Content archive and recovery for published digital assets

Data flow: OpenText TeamSite - LiveSite Content Services to FTP

Published assets and page packages can be exported from OpenText TeamSite - LiveSite Content Services to an FTP repository for archival, backup, or downstream reuse. This is valuable for compliance, disaster recovery, and long-term retention of campaign materials or regulated content.

• Creates a simple file-based archive for published content
• Supports recovery of assets after site incidents or accidental deletion
• Helps meet retention requirements in regulated industries

6. Batch delivery of content feeds to legacy downstream systems

Data flow: OpenText TeamSite - LiveSite Content Services to FTP

When legacy systems, print vendors, or external publishing partners cannot consume APIs, OpenText TeamSite - LiveSite Content Services can export content packages or structured feeds to FTP. These files can then be picked up by downstream systems for reuse in print catalogs, kiosks, mobile apps, or offline publishing workflows.

• Extends digital content to non-API consumers
• Supports enterprise environments with mixed modern and legacy platforms
• Reduces manual reformatting of content for downstream channels

7. Approval-driven publishing workflow with file handoff

Data flow: Bi-directional

Business users can place draft content or supporting files on FTP for review, while OpenText TeamSite - LiveSite Content Services manages approval, rendering, and publication. After approval, the final published package or status file can be written back to FTP for notification to upstream teams or external vendors. This creates a practical bridge between file-based intake and controlled digital publishing.

• Improves visibility across content operations and external contributors
• Supports status-based handoff between teams
• Reduces publishing errors by separating draft intake from final release

8. High-volume campaign asset distribution to multiple web properties

Data flow: FTP to OpenText TeamSite - LiveSite Content Services

For enterprise campaigns that require the same large set of assets across multiple websites or portals, FTP can serve as the central delivery mechanism. OpenText TeamSite - LiveSite Content Services can ingest the files and publish them to multiple branded properties, ensuring consistent campaign execution across business units or regions.

• Supports centralized campaign operations
• Reduces duplication of effort across web teams
• Ensures consistent asset usage across multiple digital properties