OpenText Developer Admin - IM Developer Administration - Kentico Integration and Automation

Common Integration Use Cases Between OpenText Developer Admin - IM Developer Administration and Kentico

Below are practical integration scenarios that connect OpenText Developer Admin - IM Developer Administration with Kentico to improve content operations, customer experience delivery, and integration governance.

• 1. Controlled API and credential provisioning for Kentico integrations

  Direction: OpenText Developer Admin - IM Developer Administration to Kentico

  Integration teams can use OpenText Developer Admin to manage API credentials, endpoints, and integration artifacts for Kentico-connected services such as CRM, DAM, or eCommerce systems. This supports secure separation of development, test, and production environments while reducing manual setup errors.

  Business value: Faster onboarding of new integrations, stronger governance, and lower risk of exposing production credentials during development.

• 2. Publishing approved content from OpenText-managed integration workflows into Kentico

  Direction: OpenText Developer Admin - IM Developer Administration to Kentico

  When content or integration-related assets are approved in upstream systems, OpenText-managed workflows can trigger updates to Kentico pages, landing pages, or content modules through APIs. This is useful for organizations that centralize integration orchestration in OpenText while using Kentico as the customer-facing content layer.

  Business value: Shorter content release cycles, fewer manual publishing steps, and better alignment between backend systems and digital channels.

• 3. Synchronizing customer and campaign data for personalized experiences

  Direction: Bi-directional

  Kentico can send campaign engagement data, form submissions, and website behavior into OpenText-managed integration flows, while OpenText can return enriched customer attributes from CRM or marketing systems back to Kentico. This enables more accurate segmentation and personalized content delivery on web pages and campaigns.

  Business value: Improved targeting, higher conversion rates, and a more complete customer profile across systems.

• 4. Automated content asset distribution from DAM or integration hubs into Kentico

  Direction: OpenText Developer Admin - IM Developer Administration to Kentico

  Integration teams can configure secure transfers of approved images, documents, product sheets, and other digital assets from upstream repositories into Kentico content structures. OpenText Developer Admin can manage the integration logic, credentials, and environment-specific routing needed to keep assets synchronized.

  Business value: Reduced manual asset handling, consistent brand governance, and faster campaign or site updates.

• 5. Form submission routing from Kentico to enterprise back-office systems

  Direction: Kentico to OpenText Developer Admin - IM Developer Administration

  Kentico web forms, quote requests, event registrations, and support inquiries can be routed through OpenText integration services to downstream systems such as CRM, case management, or order processing platforms. OpenText Developer Admin helps manage the integration endpoints, transformation rules, and environment controls.

  Business value: Faster lead and case processing, fewer missed submissions, and improved operational consistency across departments.

• 6. Environment-specific deployment of Kentico integration configurations

  Direction: OpenText Developer Admin - IM Developer Administration to Kentico

  Development teams can maintain separate integration configurations for Kentico test, staging, and production environments using OpenText Developer Admin. This includes API mappings, authentication settings, and message routing rules, allowing controlled promotion of changes without disrupting live sites.

  Business value: Safer releases, better change management, and reduced downtime during integration updates.

• 7. Monitoring and exception handling for Kentico-connected business processes

  Direction: Bi-directional

  Integration events originating in Kentico, such as form submissions or content updates, can be monitored through OpenText-managed administration and messaging controls. Failed transactions can be logged, retried, or routed for manual review, while Kentico can display status messages or trigger follow-up actions when processing is complete.

  Business value: Better visibility into integration health, fewer lost transactions, and improved support response times.