HTTP - OpenText Lens - Data Visibility Integration and Automation

Common Integration Use Cases Between HTTP and OpenText Lens - Data Visibility

1. Automated Sensitive Content Discovery via HTTP API Triggers

Data flow: HTTP ? OpenText Lens - Data Visibility

Use HTTP-based API calls to trigger OpenText Lens scans when new repositories, file shares, or cloud storage locations are added to the environment. This enables IT and compliance teams to quickly assess unstructured data for sensitive, redundant, or obsolete content without waiting for manual review cycles.

• Triggers can be initiated from onboarding workflows, migration projects, or scheduled governance jobs.
• Supports faster identification of regulated content such as PII, contracts, and legal records.
• Reduces risk by ensuring new data sources are assessed early in their lifecycle.

2. Real-Time Governance Alerts from OpenText Lens to HTTP Endpoints

Data flow: OpenText Lens - Data Visibility ? HTTP

When OpenText Lens identifies high-risk content, such as exposed sensitive files or large volumes of obsolete data, it can send results to an HTTP webhook or endpoint. This allows downstream systems to automatically create tickets, notify owners, or launch remediation workflows.

• Integrates with IT service management, security operations, or workflow automation platforms.
• Enables immediate action on compliance exceptions and data risk findings.
• Improves accountability by routing findings to the correct business owner or data steward.

3. Migration Readiness Assessment for Content Platforms

Data flow: HTTP ? OpenText Lens - Data Visibility

Before migrating content from legacy file systems, ECM platforms, or shared drives, HTTP-based orchestration tools can submit source locations to OpenText Lens for analysis. The resulting visibility helps project teams classify content into migrate, archive, or delete categories.

• Supports data cleanup before cloud migration or platform consolidation.
• Reduces migration cost by excluding redundant and obsolete content.
• Improves cutover planning by identifying sensitive content that requires special handling.

4. Compliance Reporting and Evidence Collection

Data flow: OpenText Lens - Data Visibility ? HTTP

OpenText Lens findings can be exposed through HTTP endpoints and consumed by reporting portals, governance dashboards, or audit evidence repositories. This gives compliance teams a current view of where regulated data resides and how much risk exists across repositories.

• Automates evidence gathering for audits and regulatory reviews.
• Provides business leaders with measurable data risk indicators.
• Reduces manual spreadsheet-based reporting across departments.

5. Data Owner Notification and Remediation Workflow

Data flow: OpenText Lens - Data Visibility ? HTTP

When OpenText Lens flags sensitive or obsolete content, it can call an HTTP endpoint that routes the issue to the relevant data owner, records it in a workflow system, and tracks remediation status. This creates a repeatable process for cleanup and governance.

• Supports cross-functional workflows between legal, compliance, records management, and business units.
• Helps enforce retention and deletion policies more consistently.
• Improves closure rates for data remediation tasks.

6. Repository Inventory Synchronization for Governance Programs

Data flow: Bi-directional

HTTP-based integration can synchronize repository metadata, scan status, and classification results between OpenText Lens and governance or asset inventory systems. This gives program managers a centralized view of which repositories have been assessed, what risks were found, and what actions remain open.

• Maintains an up-to-date inventory of unstructured data sources.
• Helps prioritize high-risk repositories for deeper review.
• Improves coordination between infrastructure, security, and compliance teams.

7. Pre-Migration Prioritization for Cloud and Archive Projects

Data flow: HTTP ? OpenText Lens - Data Visibility ? HTTP

An HTTP orchestration layer can submit candidate repositories to OpenText Lens, receive classification results, and then automatically update migration plans. Content identified as redundant or obsolete can be excluded, while sensitive content can be routed to secure migration paths or legal review.

• Optimizes migration scope and reduces storage and transfer costs.
• Supports phased migration based on content risk and business value.
• Improves project governance by making decisions data-driven.

8. Exception Management for Policy Violations

Data flow: OpenText Lens - Data Visibility ? HTTP

OpenText Lens can send policy exception events through HTTP to case management or risk systems when content violates governance rules, such as retaining obsolete records beyond policy or storing sensitive data in unauthorized locations. This enables formal review and approval workflows.

• Creates an auditable trail for policy exceptions and remediation decisions.
• Supports enterprise risk management and records retention programs.
• Helps organizations respond faster to governance issues across distributed repositories.