Ellipse Gradient for Header

Lansweeper Integration Guide

Integrate Lansweeper Cloud inventory and security context with enterprise systems through its GraphQL API, scheduled workflows, and selected webhook-style notifications.

Lansweeper integration options at a glance

Lansweeper Cloud’s primary documented integration mechanism is its GraphQL API, which can be used to query assets, users, locations, software, operating systems, and available vulnerability information. Martini can authenticate requests with a Lansweeper API credential stored in Secrets Management, submit parameterized queries, paginate through large inventories, and map results into target systems. Webhook-style notifications may be available for selected Lansweeper features or alert scenarios, but broad event coverage is not confirmed. A general-purpose REST API, bulk API, file API, and direct database access should not be assumed. Scheduled GraphQL polling is therefore the dependable default for synchronization.

Integration pointSupported by Lansweeper?Common use casesHow Martini supports it
GraphQL APIsYesQuery Assets and related Users, Locations, Software, operating-system data, and available vulnerability information using filters, relationships, and pagination supported by the active Lansweeper schema.Martini can submit parameterized GraphQL queries from workflows, process data and errors, paginate results, and map responses into target payloads or a normalized Martini API.
REST APIsNot confirmedA generally available Lansweeper Cloud REST API was not confirmed. Any product-specific REST endpoint should be verified before designing around it.Martini can consume REST APIs when a specific Lansweeper endpoint is verified, but the integration should default to the documented GraphQL API.
Webhooks / outbound callbacksLimitedWebhook-style notifications may be available for selected Lansweeper features, alerts, or integration scenarios; coverage for all inventory changes is not confirmed.Martini can expose an API endpoint or workflow start trigger to validate an available callback, process it asynchronously, and retrieve current data when required.
Bulk / asynchronous / batch APIsNot confirmedNo separate general-purpose bulk or asynchronous export API was confirmed. Large inventories should use supported GraphQL filtering and pagination.Martini can orchestrate paged extraction, checkpoint progress, split workloads, and schedule repeatable synchronization workflows.
File / attachment APIsNot confirmedA general-purpose file or attachment API was not confirmed. Product-specific inventory exports require separate verification.Martini can process files if Lansweeper provides an approved export, but file exchange should not be assumed as the primary integration method.
AuthenticationYesLansweeper Cloud API requests use an API key or bearer-style API credential issued through the Lansweeper environment, with scope and tenant permissions requiring confirmation.Martini stores the credential in Secrets Management and injects it into authorized workflow requests without embedding secrets in workflow logic.

How Lansweeper exposes data and business events

Lansweeper GraphQL API

Lansweeper Cloud’s principal documented API mechanism is GraphQL. It can expose asset inventory and related data through schema-defined queries, relationships, filters, and pagination. The active tenant schema is authoritative for field names and availability.

Martini implementation pattern

Martini uses a workflow to authenticate against the Lansweeper GraphQL endpoint, submit a parameterized query, inspect both data and errors in the response, and transform the returned objects for a target application or normalized API.

Implementation sequence

Store the Lansweeper credential in Martini Secrets Management
Confirm the active endpoint, tenant permissions, schema fields, filters, and pagination
Submit a parameterized GraphQL query from a Martini workflow
Process both returned data and GraphQL errors
Map Assets and related objects to the target model
Persist pagination or synchronization state

Lansweeper webhook-style notifications

Webhook or outbound notification capabilities may exist for selected Lansweeper features, alerts, or integration scenarios. Research did not confirm universal notifications for asset, software, user, or vulnerability changes.

Martini implementation pattern

Where the required Lansweeper feature explicitly supports a callback, Martini can expose a controlled endpoint or workflow trigger, validate the notification, and asynchronously retrieve current Lansweeper data rather than trusting a potentially incomplete event payload.

Implementation sequence

Confirm that the required Lansweeper feature and event support callbacks
Expose a restricted Martini API endpoint or workflow start trigger
Validate the callback source and payload
Queue or asynchronously process the notification
Retrieve current Lansweeper data when the notification identifies a resource
Apply mapping, business rules, and duplicate protection

Scheduled Lansweeper synchronization

Scheduled API polling is the dependable default for synchronizing Lansweeper inventories because universal change events were not confirmed. Incremental filters, timestamps, cursors, or stable identifiers should be used where the schema supports them.

Martini implementation pattern

A Martini scheduler starts a workflow that retrieves filtered and paginated Lansweeper data, compares it with stored synchronization state or target identifiers, and writes only valid changes while recording a watermark or completed page.

Implementation sequence

Schedule the synchronization workflow
Load the last successful watermark or checkpoint
Query filtered Lansweeper data in deterministic pages
Normalize and compare stable asset identifiers
Write creates, updates, retirements, or exceptions to the target
Store the new checkpoint after successful processing

Common Lansweeper integration patterns

Pattern 1: Synchronize assets to a CMDB

When to use this pattern

Use this pattern when ServiceNow or another CMDB must reflect discovered infrastructure from Lansweeper. It supports recurring reconciliation while protecting manually managed target fields and representing assets that disappear from the source.

Integration direction
Lansweeper
Martini
ServiceNow
Example Mapping
Lansweeper FieldCanonical FieldTarget Field
Asset stable identifierexternalAssetIdcorrelation_id
Asset nameassetNamename
Operating systemoperatingSystemos
Locationlocationlocation
Martini implementation pattern

A scheduled Martini workflow pages through Assets and related operating-system, software, location, and ownership data. It validates the schema response, matches by stable Lansweeper identifier, applies create-or-update and soft-retirement rules, protects controlled ServiceNow fields, and retries transient target failures while isolating invalid records.

Martini capabilities used
  • workflows
  • API consumption
  • scheduling
  • data mapping
  • business rules
  • error handling

Pattern 2: Enrich service requests with asset context

When to use this pattern

Use this pattern when support teams need current device and ownership context in Jira Service Management or a similar service platform. Hostname can assist lookup, but stable identifiers or serial numbers should drive matching.

Integration direction
Lansweeper
Martini
Jira Service Management
Example Mapping
Lansweeper FieldCanonical FieldTarget Field
Asset stable identifiersourceAssetIdassetReference
UserownerreporterOrOwner
SoftwareinstalledSoftwareassetSoftwareContext
LocationassetLocationlocation
Martini implementation pattern

Martini receives or schedules service-request processing, queries Lansweeper for the matching asset, normalizes ownership and location values, enriches the target request or asset record, and returns a controlled outcome. Missing matches and ambiguous hostnames are routed to an exception path rather than creating duplicates.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • validation
  • business rules
  • error handling

Pattern 3: Reconcile endpoint inventories

When to use this pattern

Use this pattern when Lansweeper discovery needs to be compared with Microsoft Intune or Microsoft Configuration Manager inventories. It identifies devices found by one system but absent or inconsistent in the other.

Integration direction
Lansweeper
Martini
Microsoft Intune
Example Mapping
Lansweeper FieldCanonical FieldTarget Field
Asset stable identifiersourceAssetIddeviceReference
Device namedeviceNamedeviceName
Operating systemoperatingSystemoperatingSystem
Last seen timestampsourceLastSeenlastCheckIn
Martini implementation pattern

A Martini workflow extracts paginated Lansweeper Assets, queries the applicable Microsoft endpoint API, normalizes identifiers and timestamps, applies comparison rules, and produces approved reconciliation or exception updates. Write-back is limited to operations supported by the Microsoft product and tenant permissions, with partial failures recorded for review.

Martini capabilities used
  • workflows
  • API consumption
  • data transformation
  • business rules
  • deduplication
  • error handling

Pattern 4: Publish a normalized inventory API

When to use this pattern

Use this pattern when downstream applications should consume a stable inventory contract instead of depending directly on Lansweeper’s GraphQL schema. It is useful for controlled access, enrichment, and abstraction across multiple consumers.

Integration direction
Lansweeper
Martini
Enterprise applications
Example Mapping
Lansweeper FieldCanonical FieldTarget Field
Asset stable identifieridid
Asset namedisplayNamedisplayName
Softwaresoftwaresoftware
Vulnerabilities or security findingssecurityFindingssecurityFindings
Martini implementation pattern

Martini exposes a REST API that invokes reusable workflow logic to query Lansweeper, select approved fields, normalize the response, and apply authorization and filtering rules. The API hides Lansweeper credentials and schema details, while query failures and unavailable tenant fields produce controlled error responses.

Martini capabilities used
  • API exposure
  • workflows
  • API consumption
  • data mapping
  • authorization
  • error handling

Applications commonly integrated with Lansweeper

Lansweeper data can be incorporated into service management, endpoint-management, reporting, and observability architectures. The exact target operations depend on the receiving product’s APIs and permissions, while Martini provides the orchestration, mapping, validation, and error-handling layer.

Application Scenario Direction Martini Pattern
ServiceNow Keep Configuration Items aligned with discovered infrastructure and enrich the CMDB with operating-system, software, location, and ownership data. Lansweeper → Martini → ServiceNow A scheduled workflow queries Lansweeper Assets with related data, matches records using stable external identifiers, protects manually managed ServiceNow fields, and creates or updates Configuration Items with bounded retries and reconciliation rules.
Jira Service Management Give support teams current device, owner, location, software, and operating-system context when handling incidents and service requests. Lansweeper → Martini → Jira Service Management Martini retrieves selected Lansweeper asset data, matches devices by verified identifiers such as serial number or vendor identifier, and enriches Jira requests or synchronizes selected information into Jira Assets.
Microsoft Intune Compare Lansweeper-discovered devices with Microsoft-managed endpoint inventories to identify coverage gaps and inconsistent ownership or operating-system data. Lansweeper → Martini → Microsoft Intune A workflow extracts Lansweeper Assets, queries the applicable Microsoft endpoint API, normalizes identifiers and status values, and produces reconciliation or exception updates according to the permitted write-back model.
Microsoft Power BI Create reporting datasets for asset coverage, software deployment, lifecycle status, location distribution, and inventory trends. Lansweeper → Martini → Microsoft Power BI Martini periodically queries and pages through Lansweeper data, converts it into reporting-oriented dimensions and facts, preserves stable keys, and sends the result to an approved Power BI ingestion or storage endpoint.
Splunk Enrich operational or security analytics with asset ownership, criticality, software, operating-system, and location context. Lansweeper → Martini → Splunk A workflow extracts selected Lansweeper inventory and security context, applies privacy and field-selection rules, transforms the payload to the target ingestion model, and retries transient delivery failures.
Datadog Add discovered asset and ownership context to observability data and support inventory-aware operational analysis. Lansweeper → Martini → Datadog Martini periodically retrieves relevant Lansweeper objects, normalizes identifiers and tags, and sends approved inventory context to the selected Datadog ingestion endpoint while recording delivery state.

How to build a Lansweeper integration in Martini

Objective

Establish access to the Lansweeper Cloud GraphQL API without embedding credentials in workflow definitions.

Instructions in Martini

  • Confirm the Lansweeper endpoint, tenant access, credential format, scopes, and available schema.
  • Store the API credential in Martini Secrets Management.
  • Configure authorization headers through secure environment configuration.
  • Use the least-privileged credential required by the integration.

Objective

Select a trigger that matches the confirmed Lansweeper capability and required synchronization latency.

Instructions in Martini

  • Use a scheduler for dependable inventory synchronization.
  • Use a callback or webhook trigger only when the required Lansweeper feature explicitly supports it.
  • Define the expected frequency, overlap protection, and initial synchronization behavior.

Objective

Read current Lansweeper data efficiently and safely from the GraphQL schema.

Instructions in Martini

  • Build a parameterized GraphQL query for the required Assets and related objects.
  • Use supported filters, deterministic pagination, and incremental timestamps where available.
  • Request only the fields required by the target process.
  • Inspect both the data and errors portions of each GraphQL response.

Objective

Coordinate extraction, enrichment, transformation, target writes, and synchronization state in a maintainable Martini workflow.

Instructions in Martini

  • Separate retrieval, normalization, matching, target delivery, and checkpoint logic.
  • Persist page progress or a synchronization watermark for long-running jobs.
  • Route invalid records and target failures to an exception path.
  • Use reusable workflow logic for shared inventory and identity handling.

Objective

Convert Lansweeper’s schema and values into a target-specific canonical model.

Instructions in Martini

  • Preserve stable Lansweeper identifiers and source timestamps.
  • Normalize dates, time zones, operating-system labels, software versions, and locations.
  • Map Users, Locations, Software, and security findings only when available and permitted.
  • Keep source values where traceability is required.

Objective

Ensure that synchronization behavior is safe, idempotent, and aligned with target ownership rules.

Instructions in Martini

  • Match by stable asset identifiers rather than hostname alone.
  • Define create, update, inactive, retired, and missing-asset behavior.
  • Protect manually managed target fields from automated overwrites.
  • Apply privacy, filtering, deduplication, and reconciliation rules.

Common Lansweeper data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
AssetsRepresent discovered hardware, virtual machines, cloud resources, and other technology assets for inventory and reconciliation.ServiceNow, Jira Service Management, Microsoft Intune, Microsoft Power BIMartini queries Assets with only required fields, preserves the stable Lansweeper identifier, normalizes status and timestamps, applies deduplication rules, and performs idempotent target updates.
UsersAssociate people or ownership information with assets and inventory records.ServiceNow, Jira Service Management, Microsoft Power BIMartini validates user relationships, applies privacy and field-selection rules, resolves target identities where possible, and retains source identifiers for traceability.
LocationsProvide physical or logical location context for discovered assets and reporting.ServiceNow, Microsoft Power BI, SplunkMartini normalizes location labels and hierarchies, maps them to target reference data, and routes unresolved locations for exception handling.
SoftwareDescribe installed software and software inventory associated with discovered assets.ServiceNow, Microsoft Power BI, Splunk, DatadogMartini normalizes product names and versions, links software to stable asset identifiers, filters sensitive fields, and loads target-specific inventory models.
Operating systemsCapture operating-system information associated with discovered assets for management, reporting, and compliance context.ServiceNow, Microsoft Intune, Microsoft Power BIMartini standardizes operating-system labels and versions, compares values with target inventories, and records discrepancies without overwriting protected target fields.
Vulnerabilities or security findingsProvide security-related information associated with assets where available under the subscribed Lansweeper capabilities.Splunk, Datadog, ServiceNowMartini confirms field availability in the tenant schema, limits sensitive output, maps severity and asset references, and handles partial GraphQL responses explicitly.

Authentication and security considerations

Credential protection

Lansweeper Cloud API access uses an API key or bearer-style credential. Store the credential in Martini Secrets Management and inject it into workflow requests rather than embedding it in query definitions or logs.

Least privilege

Use the least-privileged Lansweeper account or API credential available for the required queries. Confirm credential scope, tenant access, available fields, and authorization-header requirements before deployment.

Controlled exposure

If Martini exposes a normalized inventory API or receives a callback, restrict access through appropriate authentication and authorization controls. Do not expose unrestricted user, device, software, or vulnerability data.

  • Use environment-specific secrets and rotate credentials according to organizational policy.
  • Remove credentials and sensitive inventory fields from diagnostic logs.
  • Apply target-specific filtering and privacy rules before forwarding data.

Operational considerations for Lansweeper integrations

Schema and pagination

Treat the active Lansweeper GraphQL schema as authoritative. Confirm field names, relationships, filters, query limits, pagination, and response behavior for the target tenant. Large inventories should be processed in deterministic pages rather than one large query.

Incremental synchronization

Prefer supported updated or last-seen timestamps, cursors, or change filters. When no reliable marker exists, compare stable asset identifiers and relevant values, and define whether missing assets become inactive, retired, quarantined, or deleted.

Reliability

Use bounded retries and exponential backoff for transient failures. GraphQL responses can contain both data and errors, so record affected pages and objects without logging credentials. Store checkpoints only after successful processing.

Testing and change management

Version-control query documents, test against a non-production tenant where possible, and review schema changes as deployment-impacting changes. Normalize time zones, software versions, operating-system labels, and locations before loading target systems.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrate beyond a script

Martini coordinates Lansweeper extraction, pagination, transformation, validation, enrichment, target delivery, and synchronization state in maintainable workflows rather than concentrating all logic in a one-off script.

Control the data contract

Martini can expose a normalized REST API so downstream applications do not need to understand Lansweeper’s GraphQL schema or receive direct access to Lansweeper credentials.

Handle enterprise conditions

Reusable workflows can apply idempotency, reconciliation, privacy filtering, retries, partial-failure handling, and controlled checkpoints across multiple target systems.

  • Keep credentials and environment settings separate from implementation logic.
  • Reuse mappings and business rules across CMDB, service-management, reporting, and analytics flows.
  • Monitor workflow outcomes and troubleshoot failed pages or records without replaying successful work unnecessarily.

Frequently asked questions

How can Lansweeper be integrated with enterprise systems?

Lansweeper Cloud is primarily integrated through its GraphQL API. Enterprise workflows can query Assets and related Users, Locations, Software, operating-system, and available vulnerability data, then map the results into service-management, endpoint-management, reporting, or analytics platforms. Scheduled polling is the dependable default; selected webhook-style notifications may be available for specific features.

Can Martini integrate with Lansweeper?

Yes. Martini can integrate with Lansweeper by consuming its documented GraphQL API, authenticating with a Lansweeper API credential, paging through inventory data, applying transformations and business rules, and writing to target systems or exposing a normalized Martini REST API. No native Martini Lansweeper connector was verified.

Do I need a connector to integrate Lansweeper with Martini?

No. A dedicated Lansweeper connector is not required. Martini can use Lansweeper’s confirmed GraphQL API and any specifically documented webhook or callback mechanism, with credentials stored securely and integration logic implemented in workflows and APIs.

Is there any extra Lonti cost to integrate Lansweeper with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Lansweeper. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Lansweeper, cloud infrastructure, target systems, or other third parties based on subscription, usage, and deployment model.

Which Lansweeper integration method should an architect use?

Use the Lansweeper Cloud GraphQL API as the primary method. Confirm the active schema, endpoint, permissions, fields, filters, and pagination behavior for the target tenant. A generally available Lansweeper Cloud REST API, SOAP API, general bulk API, and direct hosted-database access were not confirmed.

Does Lansweeper provide webhooks or events for inventory changes?

Webhook-style or outbound notifications may be available for selected Lansweeper features, alerts, or integrations, but universal events for every asset, software, user, or vulnerability change were not confirmed. Scheduled GraphQL polling with incremental filters or comparison logic is the safer default unless the required event is explicitly documented.

How should Lansweeper data be synchronized and mapped?

Use GraphQL filters, timestamps, cursors, or pagination where the active schema supports them. Match records using Lansweeper’s stable asset identifier, normalize dates, locations, operating systems, and software versions, and maintain a source-to-target identifier map. If no reliable change marker is available, compare stable identifiers and relevant values or hashes.

How does Martini handle Lansweeper errors, retries, and duplicate data?

Martini workflows can inspect both data and errors in GraphQL responses, apply bounded retries with backoff for transient failures, and avoid retrying malformed queries or authorization failures without correction. Idempotent create-or-update logic, stable external keys, checkpoints, validation, and exception handling help control duplicates and partial failures.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Build a Lansweeper integration with Martini

Use Martini to connect Lansweeper Cloud’s GraphQL API with your enterprise applications through secure, observable, and maintainable workflows.

EXPLORE MARTINI
BOOK A DEMO