Skip to content

Cookie Settings

This site uses cookies that need consent.

ServiceNow Destination Connector for CI Synchronizer

ServiceNow is a cutting-edge cloud platform revolutionising business workflows. Core to its suite of modules and applications is the CMDB (Configuration Management Database), a pivotal element for orchestrating IT operations. Integrating CI Synchronizer with ServiceNow yields incredible advantages, transforming your IT operations with unparalleled efficiency and precision.

The ServiceNow connector requires almost no ServiceNow configuration: just a set of user credentials (and optional OAuth setup) to be up and running.

  • No ServiceNow ITOM (IT Operations Management) license required.

  • No configuration of ServiceNow IRE rules required.

  • Does not require custom applications to be installed and does not require custom tables/fields to be created.

  • CI Synchronizer can be configured to cater for ServiceNow CMDB customisations.

  • The ServiceNow connector supports ingestion of data from any of the CI Synchronizer Source Connectors.

App screenshot
Autonomous Correlation
CI Synchronizer effortlessly links with your CMDB (Configuration Management Database) by autonomously correlating with existing records through customisable search rules.
Comprehensive Reference Data
CI Synchronizer seamlessly automates the generation of essential reference data, encompassing choice lists, vendors, models, and more, ensuring a comprehensive, accurate and effortless integration.
Everything is Related
CI Synchronizer automatically synchronises base-asset records, related lists, and relationships. Feel ultimate confidence in the accuracy and richness of your CMDB to drive your IT operations.
Continuous Data Refresh
CI Synchronizer actively preserves the accuracy and freshness of your CMDB by automatically retiring CIs (Configuration Items) that are no longer detected by the source system.

Frequently Asked Questions

Yes. CI Synchronizer has a highly customisable rules engine. Such changes are made by Syncfish.

Yes. CI Synchronizer can detect which source records have changed since the previous synchronisation job and only sync the newly changed source data.

Yes. CI Synchronizer automatically creates a large number of relationships in the CMDB by analysing dependencies between the source data. This is a fully automated and dynamic feature and allows organisations to use ServiceNow’s depending mapping features. There are tremendous benefits to processes such as Change Management, Incident Management, Problem Management and more.

No. CI Synchronizer uses its own correlation engine which handles many more record types than IRE (Identification and Reconciliation Engine). The CI Synchronizer correlation rules can be customised if needed (though this is rarely required as the correlation rules have been highly tuned).

No, it does not.

No, it does not. CI Synchronizer uses the ServiceNow REST APIs to insert/update CI records in ServiceNow.

No, it does not.

No custom tables are required, unless you are synchronizing Digital Certificate data or CVE data from Lansweeper in which case Syncfish will discuss the options for persisting those record sets in a suitable table in ServiceNow.

CI Sync uses the OOTB ServiceNow REST APIs which do not require an ITOM licence. If an organization starts using additional ServiceNow features that take advantage of the source data being sync’d into the CMDB, then naturally the organization needs to licence such features.

CI Sync only updates the ServiceNow CMDB_CI_* tables. However, ServiceNow’s OOTB business rules automatically sync data bi-directionally between the CMDB CI tables and the Asset (ALM) tables. Therefore, CI Synchronizer ultimately helps to deliver data into your ServiceNow CMDB and Asset tables.

Yes. CI Synchronizer will correlate with existing CIs in your CMDB. Also, CI Synchronizer can use “split transform maps” which means different rules can be applied to insert vs update events.

Yes. Please use the “Organise a Demo” button or visit the Contact Us page to book a time to meet with one of the Syncfish team.

No. CI Synchronizer has an extensible multi-source/multi-destination architecture. The most common destination used is ServiceNow and there are a variety of Source connectors (with Lansweeper On-Premise being the most popular).

No. Each customer is provisioned with a dedicated CI Synchronizer instance.

No. The source asset data (read from the relevant source system by one of the CI Synchronizer connectors) is transited through your dedicated CI Synchronizer instance then deleted after it’s been processed into ServiceNow.

Many! Check out each source connector page for details of the supported assets and other records.

Throughput is affected by factors outside of the control of CI Synchronizer, however we see a typical throughput of between 200,000 and 400,000 records per hour (and even higher rates are possible).

Ultimately the customer decides, however Syncfish recommends hosting each customer instance physically close to the location of their ServiceNow instance (for best performance). It can be hosted in most/all Azure Regions globally (it is still hosted/managed/maintained by Syncfish, but the customer decides which geography it is physically located in).

Yes. The CI Synchronizer rules can be customised on a customer-by-customer basis to meet the unique needs of your customised CMDB design.

    Find out more

    Talk with us to find discover CI Synchronizer, the available connectors and the services we offer to help you achieve CMDB excellence.

    Book a Demo

    Schedule a demo. See up close how CI Synchronizer works and how quickly you can start syncronising your IT Asset data into your CMDB.

    Request a Trial

    Syncfish offers customers the chance to trial CI Synchronizer. Contact Sales or book a demo to find out how to get setup with a trial.