We use cookies on our website to analyze website usage and to help secure the website against misuse. Advertising and functional cookies are not used in our site or our web application products.
By clicking “Accept Essential Cookies Only”, you consent to us placing these cookies.
ServiceNow is widely used as the Configuration Management Database and as a platform for change, incident and request management. Many organisations that run ServiceNow also run a specialised IT Asset Management toolset alongside it, to handle detailed hardware and software asset management, licence entitlement tracking, software compliance calculation, and the day-to-day procurement, deployment and disposal operations that an asset team needs to run. xAssets is designed to fit into that pattern.
The xAssets integration with ServiceNow is designed for organisations that want to keep ServiceNow as the CMDB and the service desk platform, and add purpose-built ITAM and SAM capabilities alongside it. This article describes how the integration works and the reasons customers use it.
A CMDB typically aggregates data from many upstream sources — Tanium, SCCM, Intune, discovery tools, manual entry and spreadsheet imports. Because each source uses its own conventions, the same manufacturer can end up represented several different ways in the combined dataset (for example "Dell", "Dell Inc." and "Dell Computer Corp"), and software titles can show similar variation. This is a well-known characteristic of aggregated asset data in general, and it is something xAssets is specifically designed to tidy up.
xAssets adds three complementary capabilities to a ServiceNow estate:
Not only can we recognise and normalise the data pulled from ServiceNow, we can also push cleaned, consolidated records back into the SerivceNow CMDB, using our recognition engine in reverse, so it translates our lookups to ServiceNow lookups.
The integration uses the ServiceNow Table API and works in both directions.
Pull — xAssets reads configuration items from the CMDB tables (computers, network equipment, printers, virtual machines, servers and so on), together with their installed software records. Data is loaded into the xAssets Network Discovery pipeline, where the same matching, classification and normalisation rules apply that are used for every other discovery source.
Push — xAssets can write back into the CMDB. Cleaned asset data, normalised manufacturers and models, software catalogue entries and install records, network adapters and file systems are posted to the appropriate ServiceNow tables using PATCH for updates and POST for new records. This allows ServiceNow to remain the CMDB of record while benefiting from the data quality work done in xAssets.
xAssets uses its recognition engine in reverse — instead of only cleaning incoming data, it reads the CMDB's existing manufacturer and model records, runs them through the recognition engine, and produces a canonical value for each. Once that mapping exists, every subsequent asset push uses the resolved ServiceNow sys_id for the canonical name, which helps keep the CMDB tidy over time.
The same mechanism applies to software titles. Aggregated variations of the same product name are consolidated into a single recognised product record, which is a useful starting point for licence compliance reporting.
For many ServiceNow customers the stronger driver for adding xAssets is Software Asset Management. xAssets has a rewritten SAM engine with a specific set of capabilities that customers often find useful to have alongside their existing tooling.
The input to all of this is the installed software data pulled from ServiceNow — along with any other source connected to xAssets — and the licence entitlement records maintained in xAssets. The output is a compliance position per product, with a full transaction history behind every number.
xAssets provides a set of asset management workflows out of the box, tailored to the operational needs of an asset team. Customers use these for the procurement, deployment and disposal steps that sit around their service management processes.
The workflows are configured through menus and forms inside xAssets, which means an asset administrator can adjust them as processes evolve:
A common pattern is to keep ServiceNow as the user-facing front door — incidents, service requests and change records continue to originate there — and to hand off to xAssets for the asset-specific steps. Where closer coupling is useful, xAssets can push status updates back to the ServiceNow record so the full history remains visible in both systems.
Customers rarely want to move away from ServiceNow as the CMDB. The push pipeline is designed so they do not have to. Assets discovered by xAssets from any source — ServiceNow itself, Tanium, SCCM, Intune, JAMF, Kandji, Network Discovery, manual entry or other integrations — can be pushed into the appropriate ServiceNow CI class, along with their network adapters, file systems, installed software catalogue entries and install records. ServiceNow sees a consolidated, normalised view rather than a patchwork of source-specific duplicates.
The integration maps to the standard ServiceNow CI class hierarchy — computers, servers, virtual machines, network equipment
and printers — and can be extended to custom CI classes where required. Installed software records are pushed to
cmdb_software_instance, with the software catalogue populated in cmdb_ci_spkg. Network adapters and file
systems are mapped to their respective child CI tables.
On the pull side, any CI class exposed through the Table API can be imported. The field map is configurable and the same matching rules that xAssets uses for other sources apply, so a device that exists in ServiceNow and in Tanium or Intune is matched rather than duplicated.
Once ServiceNow data is in xAssets, the xAssets reporting suite is available on top of it — licence compliance, refresh planning, warranty expiry, depreciation, cost by department, devices not seen for N days, and so on. Custom dashboards and queries can be built against the same consolidated dataset, and the xAssets REST API and MCP server can expose this data to other systems or to AI assistants.
The ServiceNow integration with xAssets is less about collecting asset data — ServiceNow already holds it — and more about adding specialised capabilities alongside. It brings data normalisation, a modern temporal SAM engine and a set of configurable asset workflows to the estate. ServiceNow remains the CMDB of record and the service desk platform, and xAssets runs the detailed asset management and software compliance work alongside it.
Free instances are free forever and can show demo data or your data.
