FTP - OpenText TeamSite Authoring Services Integration and Automation

Common Integration Use Cases Between FTP and OpenText TeamSite Authoring Services

• Bulk content asset ingestion from FTP into TeamSite
  Marketing teams can receive large batches of approved images, PDFs, product sheets, and localized media files from agencies or production vendors via FTP/SFTP, then automatically import them into OpenText TeamSite Authoring Services for content assembly and publishing. This reduces manual upload effort, speeds campaign launches, and ensures assets are available in the correct repository for editorial workflows.
• Scheduled export of approved web content packages to FTP for downstream publishing
  OpenText TeamSite Authoring Services can export finalized page content, HTML fragments, media bundles, or structured content packages to an FTP location for consumption by downstream web delivery platforms, CDNs, or legacy publishing systems. This is useful when the web experience stack includes external rendering or deployment tools that still rely on file-based handoff.
• Localized content distribution to regional teams and agencies
  Global marketing organizations can use TeamSite to manage master content and then push region-specific content packages to FTP for local agencies, translators, or country teams to review, adapt, and return. This supports controlled localization workflows while preserving governance and version consistency across markets.
• Automated media exchange for high-volume digital campaigns
  When campaigns require large video files, high-resolution imagery, or rich media libraries, FTP can serve as the transfer mechanism between production teams and TeamSite. Assets uploaded to FTP can be picked up by automated jobs and attached to content records in TeamSite, helping teams manage large file volumes without overloading manual content operations.
• Content approval handoff from TeamSite to external production vendors
  After content is approved in TeamSite, the system can generate export files and place them on FTP for external vendors such as print houses, localization providers, or creative agencies. This enables a controlled handoff of final content versions, reduces email-based file sharing, and creates a repeatable process for partner collaboration.
• Legacy system bridge for structured content migration
  Organizations modernizing their digital experience stack can use FTP as a bridge to move legacy content exports, metadata files, and media archives into TeamSite. This is especially valuable during migration projects where source systems can only produce batch files, allowing content teams to gradually onboard assets into a governed authoring environment.
• Backup and archival of published content packages
  TeamSite can periodically export approved content, templates, and associated assets to FTP-based archive storage for retention, audit, or disaster recovery purposes. This provides a simple and reliable backup path for regulated industries or teams that need to preserve published content snapshots for compliance and rollback.