.png)
ServiceNow IT Asset Management Integration Guide
Integrate ServiceNow IT Asset Management with enterprise applications through REST and SOAP APIs, import interfaces, attachment APIs, and configured outbound callbacks.
ServiceNow IT Asset Management integration options at a glance
ServiceNow IT Asset Management primarily integrates through REST APIs, including the Table API, Import Set API, Attachment API, Aggregate API, and configured scripted REST APIs. SOAP web services remain available for legacy or specialized enterprise integrations. ServiceNow can also send webhook-style outbound callbacks through REST messages, SOAP messages, business rules, and Flow Designer configurations for selected events. OAuth 2.0 and Basic Authentication are commonly used, with roles, ACLs, scopes, and instance policies controlling access. Martini can consume these interfaces, receive callbacks, orchestrate workflows, transform payloads, and expose controlled APIs for downstream systems.
| Integration point | Supported by ServiceNow IT Asset Management? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | ServiceNow provides Table API, Import Set API, Attachment API, Aggregate API, and scripted REST APIs for ITAM reads, writes, imports, attachments, queries, and controlled business operations. | Martini can consume ServiceNow REST endpoints, transform requests and responses, apply business rules, and expose reusable APIs or workflows around them. |
| SOAP APIs | Legacy | ServiceNow SOAP web services support direct table and import-oriented integrations, particularly for existing enterprise systems that cannot consume REST. | Martini can consume SOAP services and map XML requests and responses, while REST should generally be evaluated first for new implementations. |
| Webhooks / outbound callbacks | Limited | Configured business rules, flows, REST messages, SOAP messages, or scripted outbound logic can send callbacks for selected ITAM events such as asset updates or license changes. | Martini can expose an API or receive webhook-style callbacks through a workflow, validate the event, retrieve current data, and continue downstream processing. |
| Bulk / async / batch APIs | Yes | The Import Set API loads external data into import-set tables for transform maps, validation, coalescing, and controlled ingestion into production tables. | Martini can batch records, call the Import Set API, monitor responses, and handle rejected rows or transformation exceptions without treating bulk loads as ordinary single-record CRUD. |
| File / attachment APIs | Yes | The Attachment API manages invoices, purchase documents, warranty files, license certificates, audit evidence, and device reports associated with ServiceNow records. | Martini can transfer files in separate workflow steps, validate content metadata, associate attachments with the correct record, and retry or quarantine failed transfers. |
| Authentication | Yes | ServiceNow supports OAuth 2.0 and Basic Authentication, with optional certificate-based controls and authorization governed by users, groups, roles, scopes, ACLs, and instance policies. | Martini can store credentials and environment configuration securely and use authenticated API workflows with least-privilege access controls. |
| Database / analytics access | Limited | The Aggregate API supports limited server-side aggregation over ServiceNow table data; direct production database access is not the normal supported integration pattern. | Martini can consume approved ServiceNow API results and aggregate responses, but should not be designed around direct SQL access to the ServiceNow production database. |
| File import/export | Limited | Controlled imports can be implemented through import sets, while attachments support files associated with records. Exact export and batch options depend on the instance and release. | Martini can orchestrate file-based preparation or attachment transfer and then invoke the appropriate ServiceNow API or import interface. |
How ServiceNow IT Asset Management exposes data and business events
ServiceNow REST APIs
ServiceNow REST APIs are the principal current integration mechanism for ITAM. The Table API supports targeted CRUD operations, while the Import Set, Attachment, Aggregate, and scripted REST APIs support controlled ingestion, files, aggregation, and custom operations.
Martini implementation pattern
Martini implementation pattern: Martini workflows authenticate to the ServiceNow instance, retrieve or submit bounded payloads, normalize reference fields and response formats, apply validation and business rules, and write results to downstream systems or expose a controlled Martini API.
Implementation sequence
ServiceNow Import Set API
The Import Set API provides a controlled path for larger or structured inbound loads. Data is placed into import-set tables and processed through transform maps that can validate, map, and coalesce records before they reach target tables.
Martini implementation pattern
Martini implementation pattern: Martini prepares batches, submits them to the Import Set API, tracks import and transformation outcomes, and routes rejected rows or coalescing conflicts to an exception workflow.
Implementation sequence
ServiceNow outbound callbacks
ServiceNow can send outbound REST or SOAP messages for selected events using business rules, Flow Designer flows, REST messages, IntegrationHub capabilities, or scripted logic. Coverage is configured per event and is not universal across ITAM tables.
Martini implementation pattern
Martini implementation pattern: Martini exposes an authenticated API endpoint or webhook workflow, validates the callback, retrieves the current ServiceNow record when necessary, and processes the event idempotently rather than trusting a notification as the complete record state.
Implementation sequence
ServiceNow SOAP web services
ServiceNow supports SOAP web services for direct table access and import-oriented integrations. SOAP is generally a legacy or compatibility option for systems that cannot consume REST.
Martini implementation pattern
Martini implementation pattern: Martini consumes the SOAP operation, transforms XML into a canonical representation, applies the same validation and idempotency controls used for REST flows, and maps the result to the target system.
Implementation sequence
ServiceNow Attachment API
The Attachment API manages files associated with ServiceNow records, including invoices, warranty documents, license certificates, audit evidence, and device reports. Attachment processing is separate from ordinary table JSON updates.
Martini implementation pattern
Martini implementation pattern: Martini first establishes or locates the target record, validates file metadata and content policy, transfers the attachment, and records the file identifier and outcome for retry or audit purposes.
Implementation sequence
Common ServiceNow IT Asset Management integration patterns
Pattern 1: Synchronize hardware assets with endpoint platforms
When to use this pattern
Use this pattern when ServiceNow should reconcile governed asset and CMDB data with endpoint inventory from Microsoft Intune, Microsoft Configuration Manager, or Jamf Pro. It supports scheduled incremental synchronization and selected event-driven updates.
Integration direction
Example Mapping
| ServiceNow IT Asset Management Field | Canonical Field | Target Field |
|---|---|---|
| device.serialNumber | asset.serialNumber | alm_hardware.serial_number |
| device.userPrincipalName | asset.assignedUser | alm_hardware.assigned_to |
| device.complianceState | asset.lifecycleStatus | alm_hardware.install_status |
| device.model | asset.modelName | cmdb_model.name |
Martini implementation pattern
Martini retrieves incremental endpoint data, normalizes identifiers, resolves users and models, and matches on serial number, asset tag, or external device ID. The workflow applies status and ownership rules, updates alm_hardware and related cmdb_ci records, and retries transient failures while routing ambiguous matches to an exception path.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- business rules
- idempotency
- error handling
Pattern 2: Coordinate employee lifecycle and asset assignment
When to use this pattern
Use this pattern when Workday or Microsoft Entra ID changes should assign, update, or reclaim ServiceNow assets as employees join, move departments, or leave the organization.
Integration direction
Example Mapping
| ServiceNow IT Asset Management Field | Canonical Field | Target Field |
|---|---|---|
| worker.employeeId | person.externalId | sys_user.employee_number |
| worker.department | person.department | sys_user.department |
| worker.lifecycleStatus | person.employmentStatus | sys_user.active |
| assignedAsset.assetTag | asset.assetTag | alm_asset.asset_tag |
Martini implementation pattern
A Martini workflow receives or retrieves worker changes, locates the ServiceNow user, queries assigned alm_asset or alm_hardware records, and applies joiner, mover, or leaver rules. Missing users, duplicate assignments, and unresolved references are held for review rather than silently creating inconsistent ownership.
Martini capabilities used
- event-driven workflows
- API consumption
- reference resolution
- data mapping
- conditional routing
- exception handling
Pattern 3: Reconcile software licenses and compliance
When to use this pattern
Use this pattern when ServiceNow license entitlements need to be compared with software discovery, procurement, or allocation data on a recurring basis.
Integration direction
Example Mapping
| ServiceNow IT Asset Management Field | Canonical Field | Target Field |
|---|---|---|
| software.productId | license.productIdentifier | alm_license.software_product |
| software.entitlementCount | license.entitlementQuantity | alm_license.quantity |
| software.allocatedCount | license.allocatedQuantity | alm_license.allocated |
| software.renewalDate | license.renewalDate | alm_license.renewal_date |
Martini implementation pattern
Martini schedules incremental discovery and procurement retrieval, maps products and entitlements, calculates variances, and submits larger loads through the Import Set API or targeted updates through the Table API. The workflow records reconciliation results, sends compliance exceptions downstream, and transfers evidence through the Attachment API when required.
Martini capabilities used
- scheduled workflows
- bulk API consumption
- data transformation
- business rules
- file handling
- monitoring
Pattern 4: Synchronize procurement, warranties, and contracts
When to use this pattern
Use this pattern when SAP S/4HANA or another procurement application supplies purchase orders, received quantities, vendors, warranties, or contract terms for ServiceNow ITAM.
Integration direction
Example Mapping
| ServiceNow IT Asset Management Field | Canonical Field | Target Field |
|---|---|---|
| purchaseOrderLine.externalId | procurementLineId | alm_asset.u_external_procurement_id |
| purchaseOrderLine.material | asset.modelIdentifier | cmdb_model.model_number |
| receipt.quantity | asset.receivedQuantity | alm_asset.quantity |
| contract.expiryDate | contract.expiryDate | ast_contract.ends |
Martini implementation pattern
Martini orchestrates purchase-order and receipt retrieval, normalizes vendor and model references, and uses an external procurement-line identifier as an idempotency key. It creates or updates ServiceNow records, applies quantity and warranty rules, transfers supporting documents separately, and retries transient API failures.
Martini capabilities used
- workflow orchestration
- API consumption
- data mapping
- idempotency
- business rules
- attachment processing
- retry handling
Applications commonly integrated with ServiceNow IT Asset Management
ServiceNow IT Asset Management can exchange inventory, identity, procurement, contract, and lifecycle information with adjacent enterprise applications. The exact scope depends on the licensed ServiceNow applications, instance configuration, table permissions, and APIs exposed by each counterpart.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Microsoft Intune | Exchange managed-device inventory, compliance state, serial numbers, ownership, and lifecycle information with governed ServiceNow asset records. | Microsoft Intune → Martini → ServiceNow IT Asset Management | Martini retrieves or receives device data, matches serial numbers or device identifiers, maps endpoint status to Hardware Asset and Configuration Item fields, and applies idempotent create-or-update rules. |
| Microsoft Configuration Manager | Reconcile discovered hardware and software inventory with ServiceNow Hardware Asset and Configuration Item records. | Microsoft Configuration Manager → Martini → ServiceNow IT Asset Management | A scheduled Martini workflow retrieves incremental inventory, normalizes identifiers and model data, compares existing ServiceNow records, and writes controlled updates through the Table API or Import Set API. |
| Jamf Pro | Synchronize Apple device inventory, serial numbers, assigned users, enrollment status, and lifecycle information with ServiceNow ITAM. | Jamf Pro → Martini → ServiceNow IT Asset Management | Martini consumes Jamf data, resolves users and models, maps device state to alm_hardware and related cmdb_ci records, and routes unmatched or duplicate devices for review. |
| SAP S/4HANA | Exchange procurement, purchase orders, vendors, goods receipts, contracts, and asset-related financial information with ServiceNow. | SAP S/4HANA → Martini → ServiceNow IT Asset Management | Martini orchestrates purchase and receipt flows, maps purchase-order line identifiers and vendor data, creates or updates ServiceNow asset and contract records, and stores external keys for duplicate prevention. |
| Workday | Synchronize worker, department, manager, location, and employment-status data used to assign or reclaim ServiceNow assets. | Workday → Martini → ServiceNow IT Asset Management | Martini receives or retrieves worker changes, locates the corresponding ServiceNow user, queries assigned alm_asset or alm_hardware records, and applies joiner, mover, and leaver business rules. |
| Microsoft Entra ID | Reconcile users, groups, departments, and identity lifecycle events with ServiceNow users and asset assignments. | Microsoft Entra ID → Martini → ServiceNow IT Asset Management | A Martini workflow retrieves identity changes, resolves ServiceNow user references, validates ownership, and updates assignment-related fields while recording unresolved identities for exception handling. |
| Salesforce | Exchange customer, account, service, or installed-asset information where ServiceNow supports customer operations or field-service processes. | Salesforce → Martini → ServiceNow IT Asset Management | Martini receives selected Salesforce changes or retrieves them on a schedule, maps account and installed-asset data to ServiceNow models, and applies routing and reconciliation rules before writing through ServiceNow APIs. |
| Jira | Coordinate engineering work involving configuration items, hardware defects, or asset-related change tasks. | ServiceNow IT Asset Management → Martini → Jira | Martini translates selected ServiceNow asset or change events into Jira issues, maps lifecycle and status values, synchronizes approved updates, and prevents duplicate issue creation with stored cross-system identifiers. |
How to build a ServiceNow IT Asset Management integration in Martini
Objective
Establish controlled access to the ServiceNow instance and any adjacent systems using the authentication methods and permissions approved for the integration.
Instructions in Martini
- Configure the ServiceNow base URL and environment-specific settings
- Use OAuth 2.0 or Basic Authentication according to the instance policy
- Store credentials and tokens in secure Martini configuration or secrets
- Validate required roles, table ACLs, field ACLs, scopes, and domain restrictions
Objective
Select a schedule, inbound callback, or API request that matches the synchronization latency and event coverage required by the process.
Instructions in Martini
- Use a scheduler for incremental or reconciliation workflows
- Expose a Martini API or webhook workflow for configured ServiceNow callbacks
- Document the exact ServiceNow business rule, flow, or outbound message that emits events
- Define the initial synchronization and replay behavior
Objective
Read the required ServiceNow tables or accept the inbound event while limiting payload size and preserving a reliable checkpoint.
Instructions in Martini
- Use Table API queries with bounded fields and result sets
- Apply sysparm_query, sysparm_limit, and sysparm_offset where appropriate
- Use sys_updated_on with a tie-breaker such as sys_id for incremental reads
- Retrieve related records and attachments as separate workflow operations
Objective
Coordinate lookups, enrichment, validation, target writes, and ServiceNow updates as a maintainable Martini workflow.
Instructions in Martini
- Separate extraction, transformation, business rules, and delivery stages
- Resolve users, groups, companies, models, locations, and configuration item references deliberately
- Route missing references and business exceptions to an explicit handling path
- Persist correlation identifiers and checkpoints
Objective
Convert ServiceNow table, reference, JSON, XML, import-set, or attachment payloads into the canonical and target-specific models.
Instructions in Martini
- Map actual objects such as alm_hardware, alm_asset, alm_license, cmdb_ci, cmdb_model, and ast_contract
- Normalize sys_id, display values, dates, states, identifiers, and quantities
- Use canonical fields to keep adjacent application mappings independent
- Validate required fields before invoking create or update operations
Objective
Enforce ownership, lifecycle, reconciliation, compliance, and duplicate-prevention decisions before changing records.
Instructions in Martini
- Match on serial number, asset tag, external license ID, or procurement-line ID
- Use coalescing or pre-query logic before creating records
- Apply joiner, mover, leaver, warranty, renewal, and compliance rules
- Avoid overwriting calculated or process-controlled ServiceNow fields without confirming side effects
Common ServiceNow IT Asset Management data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Hardware Asset (alm_hardware) | Synchronize laptops, servers, mobile devices, ownership, assignment, lifecycle state, serial numbers, and stock information. | Microsoft Intune, Microsoft Configuration Manager, Jamf Pro, Workday, Microsoft Entra ID | Martini retrieves or receives asset data, matches serial numbers, asset tags, or external identifiers, resolves references, and performs validated create-or-update operations. |
| Asset (alm_asset) | Exchange common asset attributes and assignment information across asset types. | Workday, Microsoft Entra ID, SAP S/4HANA, endpoint-management platforms | Martini maps canonical asset fields to ServiceNow fields, applies lifecycle and ownership rules, stores sys_id values, and prevents duplicate creation with external keys. |
| Software License (alm_license) | Synchronize license entitlements, allocations, software products, compliance information, and renewal data. | Software-discovery platforms, SAP S/4HANA, procurement systems, reporting platforms | Martini can use scheduled workflows, Import Set API loads, targeted Table API updates, and Attachment API transfers for evidence or certificates. |
| Configuration Item (cmdb_ci and child tables) | Reconcile assets with infrastructure records, operational ownership, discovered devices, and configuration relationships. | Microsoft Configuration Manager, Microsoft Intune, Jamf Pro, Jira | Martini resolves configuration item identifiers and reference fields, applies reconciliation rules, and separates inventory changes from governed CI updates. |
| Asset Model (cmdb_model) | Map manufacturer, model, product, and model-category information used by hardware and software assets. | Endpoint-management platforms, procurement systems, SAP S/4HANA | Martini normalizes manufacturer and model values, looks up or creates approved model references where permitted, and routes ambiguous matches for review. |
| Contract (ast_contract) | Exchange maintenance, lease, warranty, vendor, renewal, and contract-term information. | SAP S/4HANA, procurement systems, Salesforce, document repositories | Martini maps contract identifiers and dates, applies renewal or expiration rules, and transfers supporting documents separately through the Attachment API. |
Authentication and security considerations
Authentication and authorization
ServiceNow supports OAuth 2.0 and Basic Authentication for API access, with certificate-based controls available in some configurations. Access is additionally governed by users, groups, roles, OAuth scopes, application scopes, table ACLs, field ACLs, and instance security policies.
- Use a dedicated integration user with least-privilege table and field permissions.
- Store credentials, tokens, and certificates in secure Martini configuration or secrets.
- Validate read, create, update, and delete permissions separately for each ITAM object.
- Use encrypted transport and minimize personal, financial, and security-sensitive data.
Operational considerations for ServiceNow IT Asset Management integrations
Design for ServiceNow instance protection
Use bounded queries, explicit fields, pagination, and incremental watermarks instead of repeatedly reading complete tables. Coordinate large loads with the ServiceNow administrator and prefer Import Set processing where appropriate.
Control reliability and consistency
- Apply exponential backoff for 429 and transient 5xx responses.
- Use external keys and coalescing rules to prevent duplicate assets and licenses.
- Resolve sys_id, display values, and reference fields deliberately because display values may not be unique.
- Expect Table API writes to trigger business rules, flows, notifications, approvals, auditing, and other integrations.
- Test against the target release and customizations because fields, mandatory values, ACLs, state values, and relationships can vary.
- Transfer attachments separately and define file-size, content-type, duplicate, and retry policies.
Why use Martini instead of scripts or point-to-point integrations?
Maintainable integration orchestration
Martini provides a governed place to consume ServiceNow APIs, receive configured callbacks, transform ITAM payloads, apply business rules, and coordinate writes across endpoint, identity, procurement, HR, and operational systems.
More than point-to-point scripts
- Reuse workflows, mappings, validation, authentication, and error-handling logic across integrations.
- Expose a controlled Martini API when downstream applications should not connect directly to ServiceNow.
- Combine scheduled, event-driven, and API-led processing in one operational model.
- Preserve checkpoints, correlation identifiers, retries, and exception paths for reliable synchronization.
- Adapt to ServiceNow customizations and adjacent application schemas without duplicating integration logic in every script.
Frequently asked questions
ServiceNow IT Asset Management can be integrated through REST APIs such as the Table API, Import Set API, Attachment API, Aggregate API, and scripted REST APIs. SOAP web services support legacy integrations, while configured business rules, flows, REST messages, and SOAP messages can provide outbound callbacks for selected events.
Yes. Martini can consume ServiceNow REST APIs, consume SOAP services where required, receive configured outbound HTTP callbacks, transfer attachments, transform ITAM data, and orchestrate workflows across ServiceNow and other enterprise applications.
No. A dedicated ServiceNow connector is not required. Martini can integrate using ServiceNow's confirmed REST and SOAP APIs, Import Set and Attachment APIs, configured outbound callbacks, and supported authentication methods.
Lonti does not charge an additional per-connector or per-vendor fee to integrate ServiceNow IT Asset Management. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from ServiceNow, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
REST APIs are generally the preferred option for new integrations. Use the Table API for targeted CRUD operations, the Import Set API for controlled bulk ingestion and transformation, the Attachment API for files, and configured outbound callbacks for selected event-driven processes. SOAP is primarily a legacy or compatibility option.
Yes, when ServiceNow is configured to send outbound REST or SOAP requests through business rules, flows, REST messages, IntegrationHub capabilities, or scripted logic. Coverage is implementation-specific and should be defined for each event, such as hardware updates, asset assignments, license changes, or contract expiration.
Scheduled Martini workflows can use sys_updated_on with pagination and a persisted watermark for incremental synchronization. Stable keys such as serial number, asset tag, external license ID, or procurement-line ID should be used for matching and coalescing, with ServiceNow sys_id values retained after successful processing.
Martini can map ServiceNow objects and reference fields to canonical and target models, apply validation and business rules, and route failures through workflow error handling. Transient rate-limit and server errors can be retried with backoff, while ACL failures, schema mismatches, duplicate matches, and unresolved references should be recorded for corrective action.
Related Martini documentation
API Integration
Workflows
Integrate ServiceNow IT Asset Management with Martini
Use Martini to connect ServiceNow IT Asset Management with enterprise applications through governed APIs, workflows, mappings, callbacks, and secure data synchronization.