Skip to main content

ServiceNow Integration

PLANNED FEATURE

This integration is planned for a future release. The functionality described below is not yet available.

Currently, only the Xurrent integration is fully implemented and operational. For information about the available integration, please refer to the Xurrent integration documentation.

This guide covers the planned integration between Tripl-i and ServiceNow, which will enable seamless synchronization of configuration items, automated incident creation, and bidirectional data flow.

Overview

The planned Tripl-i-ServiceNow integration will provide:

  • Bidirectional CI Synchronization - Keep CMDB data in sync
  • Automated Incident Management - Create and update incidents
  • Change Request Integration - Link changes to CI relationships
  • Service Mapping Sync - Share service dependencies
  • Real-time Updates - Webhook-based synchronization

Architecture

The integration architecture will consist of:

  • Tripl-i Components:

    • CMDB
    • Discovery Engine
    • Event Manager
    • AI Agents
  • Integration Layer:

    • REST API
    • Webhooks
    • Transform Engine
    • Queue Manager
  • ServiceNow Components:

    • CMDB
    • Incident Management
    • Change Management
    • Service Mapping

Installation

When available, the installation process will include:

1. Install Tripl-i Integration App

  1. In ServiceNow, navigate to System Applications > Applications
  2. Search for "Tripl-i Integration"
  3. Click Install
  4. Follow the installation wizard
  5. Grant required permissions

2. Configure Integration User

Create a dedicated integration user in ServiceNow with appropriate roles:

  • ITIL role for incident/change management
  • Import admin role for CMDB operations
  • Web service access role
  • Integration user role

Assign necessary table permissions and access controls.

3. Generate API Credentials

Configure the integration through the Tripl-i admin interface by providing:

Configuration

Connection Settings

The integration will support comprehensive configuration:

Authentication:

  • Basic authentication
  • OAuth 2.0
  • Token-based authentication
  • SSO integration

Sync Configuration:

  • Configurable sync intervals
  • Batch processing size
  • Real-time webhook triggers
  • Selective sync filters

Field Mapping:

  • Standard field mappings
  • Custom field support
  • Attribute transformations
  • Data type conversions

Business Rules

ServiceNow business rules will enable:

  • Automatic sync triggers on CI updates
  • Conditional synchronization based on flags
  • Custom data transformations
  • Error handling and logging

Data Synchronization

CI Synchronization

The integration will synchronize configuration items bidirectionally:

From ServiceNow to Tripl-i:

  • CI attributes and properties
  • Relationships and dependencies
  • Status and lifecycle information
  • Custom fields and extensions

From Tripl-i to ServiceNow:

  • Discovered CIs
  • Relationship mappings
  • Updated attributes
  • Discovery metadata

Class Mapping

The integration will map between CI classes:

ServiceNow ClassTripl-i TypeNotes
cmdb_ci_serverserverStandard server mapping
cmdb_ci_win_serverserverWindows-specific attributes
cmdb_ci_linux_serverserverLinux-specific attributes
cmdb_ci_app_serverapplicationApplication servers
cmdb_ci_databasedatabaseDatabase instances
cmdb_ci_network_adapternetwork_interfaceNetwork components

Incident Integration

Automatic incident creation will support:

Event-to-Incident Mapping:

  • Map Tripl-i event severity to ServiceNow impact/urgency
  • Link incidents to affected CIs
  • Include AI analysis in work notes
  • Add discovery metadata
  • Set appropriate categories and subcategories

Status Synchronization:

  • Bidirectional status updates
  • Resolution synchronization
  • Assignment tracking
  • SLA adherence

Webhook Configuration

ServiceNow Webhooks

Outbound webhooks from ServiceNow will notify Tripl-i of:

  • CI creation, updates, and deletions
  • Incident status changes
  • Change request approvals
  • Relationship modifications

Tripl-i Webhooks

Inbound webhooks to ServiceNow will provide:

  • Discovery event notifications
  • CI update requests
  • Relationship change notifications
  • Status synchronization

All webhooks will be secured with:

  • Signature verification
  • Token authentication
  • IP whitelisting
  • Payload encryption

Field Mapping

Standard Field Mappings

The integration will support comprehensive field mapping:

ServiceNow FieldTripl-i FieldTransformation
sys_idexternal_idDirect mapping
namenameDisplay name
sys_class_nametypeClass type conversion
serial_numberattributes.serial_numberAttribute mapping
ip_addressattributes.ip_addressNetwork information
operational_statusstatusStatus code mapping
locationattributes.locationReference resolution

Custom Field Support

The integration will allow:

  • Custom field definitions
  • Flexible attribute mapping
  • Data transformation rules
  • Validation and constraints
  • Default value handling

Advanced Features

Service Mapping Integration

Synchronize service dependencies between platforms:

Service Hierarchy:

  • Business services
  • Technical services
  • Application components
  • Infrastructure dependencies

Relationship Types:

  • Depends on
  • Hosted on
  • Connected to
  • Uses

Change Management Integration

Link changes to Tripl-i discoveries:

Impact Analysis:

  • Identify affected CIs
  • Calculate dependency impact
  • Risk assessment
  • AI-powered recommendations

Change Tracking:

  • Link changes to discoveries
  • Track implementation status
  • Validation and rollback
  • Post-implementation review

Monitoring and Health

Health Check Endpoint

Monitor integration health:

  • ServiceNow API connectivity
  • Authentication status
  • Sync queue status
  • Error rates and latency
  • Last successful sync timestamp

Sync Status Dashboard

View synchronization metrics:

  • Pending sync items
  • Success/failure rates
  • Sync lag time
  • Data quality metrics
  • Error logs and alerts

Best Practices

When the integration becomes available, follow these best practices:

1. Data Governance

  • Define master data source for each CI type
  • Implement conflict resolution rules
  • Conduct regular data quality audits
  • Maintain data ownership documentation

2. Performance

  • Use bulk APIs for large synchronizations
  • Implement intelligent caching
  • Monitor API rate limits
  • Schedule intensive syncs during off-peak hours

3. Security

  • Use OAuth 2.0 over basic authentication
  • Encrypt sensitive field data
  • Audit all integration activities
  • Implement least-privilege access
  • Rotate credentials regularly

4. Error Handling

  • Implement retry logic with exponential backoff
  • Queue failed syncs for replay
  • Alert on critical failures
  • Log all errors with context
  • Maintain error metrics dashboard

Troubleshooting

Common Integration Issues

Authentication Errors:

  • Symptom: "401 Unauthorized" responses
  • Potential Causes: Expired credentials, incorrect OAuth configuration, locked user account
  • Resolution Steps: Regenerate OAuth tokens, verify client ID/secret, check user account status

Sync Delays:

  • Symptom: Data not syncing in a timely manner
  • Potential Causes: Large backlog, rate limiting, network issues
  • Resolution Steps: Increase batch size, implement queue prioritization, check network connectivity

Field Mapping Issues:

  • Symptom: Missing or incorrect data
  • Potential Causes: Field name changes, unmapped custom fields, data type mismatch
  • Resolution Steps: Review field mappings, update transform scripts, add data validation

Webhook Failures:

  • Symptom: Webhooks not firing
  • Potential Causes: Incorrect URL, authentication failure, firewall blocking
  • Resolution Steps: Verify webhook URL, check authentication, review firewall rules

Data Quality

Validation Rules

The integration will enforce data quality:

  • Required field validation
  • Data type checking
  • Format validation
  • Referential integrity
  • Custom business rules

Conflict Resolution

Handle data conflicts with:

  • Last-write-wins strategy
  • Configurable precedence rules
  • Manual review queues
  • Audit trail maintenance

Support and Feedback

For questions or to express interest in this integration:


Note: This document describes a planned feature. Implementation timeline and final feature set may vary. Check with your account representative for the latest information about integration availability.