Connect inventory from Lansweeper to TOPdesk Asset Management. Service Automation Suite matches devices and relationships, maps attributes and keeps agreed records current.
Service Automation Suite · Central coordination
Matching, field mapping & relationships
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Source
Devices & inventory data
Update
Assets, people & lifecycle
Select relevant inventory
Use available device attributes and the agreed scope. Define the authoritative source for each field.
Match and update
Avoid duplicate assets, update changed fields and connect the right people to their assets.
Connect records to follow-up
Connect missing data, a changed owner or an employee departure to tasks, changes or asset returns.
Maintain records
Found on the network, missing from your records.
Keep the CMDB current with discovered assets. Route discrepancies as tickets or tasks, and track ownership, software and lifecycle.
Service Automation Suite · Central coordination
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Connect your inventory to TOPdesk, HaloITSM, ServiceNow, Freshservice or Jira Service Management, for example. Compare asset data, update agreed fields and route discrepancies to the right service team. We tailor the workflow to your platform, available modules and configuration.
Keep the CMDB current
Compare discovered devices and software with configuration items. Sync agreed fields and review missing or duplicate records.
Create tickets with context
Turn an unknown device, changed status or relevant software change into a ticket or task. Include asset context and report the outcome back.
Track ownership and lifecycle
Compare owner, location and usage with service records. Route discrepancies for follow-up and record what was changed or excepted.
Handover & return
Every asset has an owner. Even after a change.
Connect devices and records to the employee and the actual handover. A missing device is not automatically a returned laptop.
Service Automation Suite · Central coordination
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Information & trigger
Relevant data or workflow status
Follow-up & feedback
Update, execute and record outcomes
Link person and asset
Combine available user and asset data with employee records.
Coordinate handover or return
Have the responsible person confirm the handover and update agreed relationships.
Keep open actions visible
Follow up missing returns and outdated relationships on reassignment or departure.
Alerts & follow-up
Give every discrepancy an owner.
Turn a relevant status or discrepancy into actionable work. Add context and route follow-up to the right team.
Service Automation Suite · Central coordination
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Information & trigger
Relevant data or workflow status
Follow-up & feedback
Update, execute and record outcomes
Receive the signal
Use the available status or event and identify repeated alerts.
Add context and routing
Connect customer, device or service context where available. Apply your priority and ownership rules.
Track resolution
Create or update a ticket and keep execution and feedback in the same process.
Assets & CMDB sync Popular
From Lansweeper to an up-to-date CMDB.
Read available data from Lansweeper and connect it to TOPdesk Asset Management or Matrix42, for example. API Composer configures retrieval and writes. DataFlow Composer prepares the right selection, field values and relationships for the CMDB.
Service Automation Suite · Central coordination
API Composer · DataFlow Composer
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Source data
Inventory and available context
Records & relationships
Agreed assets, CIs and references
Choose source, selection and matching
For Lansweeper, assess asset ID, hardware, software and discovered relationships from the available Data API or export. Define reliable matching, for example a source ID plus customer or tenant, or a serial number. A computer name alone is not always unique.
Read, combine and map
API Composer retrieves permitted data through the selected API. DataFlow Composer filters and normalises values, compares existing records and relates customer, location and person references where available. Where paginated, retrieve the complete agreed selection.
Create, update and verify
Create a missing asset or CI, or update agreed fields through the destination API. Retain source and destination IDs and check the response. Route uncertain matches for review; missing telemetry does not automatically mean deletion.
We choose data, direction and frequency based on available interfaces, modules and permissions. An existing import can remain in place; only agreed fields are updated.
Connect tickets with CC
Keep the alert and its resolution connected.
Follow up a relevant alert or discrepancy from Lansweeper in TOPdesk, Matrix42 or another service tool, for example. Collaboration Composer (CC) handles ticket collaboration; API Composer and DataFlow Composer can add device, customer and CMDB context.
Service Automation Suite · Central coordination
Collaboration Composer (CC)
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Trigger & context
Alert, reference and relevant asset
Resolution & feedback
Local ticket, owner and status
Define when a ticket is needed
Select relevant alerts or requests. Match the same source event before creating another ticket; add the correct asset, customer and service where available. An update is not automatically a new incident.
Connect tickets and working agreements
Use CC to configure which fields, comments and statuses are exchanged. Retain both ticket references and agree priority, ownership and resolution. Share internal notes and attachments only when explicitly agreed and supported.
Record confirmed progress
Return the agreed outcome and route failures for retry or review. A cleared monitoring alert does not automatically close an incident or security investigation. Configure writes back to Lansweeper only for demonstrably supported actions; otherwise retain a reference to the service ticket.
Check discrepancies Popular
Discovered, recorded and in use: do they still match?
Compare available operational data with agreed CMDB records. DataFlow Composer makes missing, duplicate or inconsistent data actionable. Define the source per field; not everything needs two-way synchronisation.
Service Automation Suite · Central coordination
DataFlow Composer · API Composer
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Compare sources
Technical status and available attributes
Review & follow up
Correct records or start a CC ticket
Define what a difference means
Agree ownership of serial number, location, user and lifecycle state, where available. Consider measurement time and source quality. A missing device is not the same as a confirmed return.
Correct only what is agreed
DataFlow Composer compares data and prepares the appropriate change. API Composer writes only permitted fields after agreed checks. Conflicting or uncertain matches remain assigned for review.
Connect exceptions to work
Let a relevant discrepancy start a ticket or task in your service workflow, using CC where needed. Retain comparison results, references and outcomes so the next run can be checked and repeat alerts reduced.
How Service Automation Suite connects data and execution
The work between your applications
Records updated. Do they match reality?
Service Automation Suite connects Lansweeper with your other applications, people and rules. Keep data aligned, work moving and outstanding actions visible.
A change, request or alert
Service Automation Suite
Data, people, assets and relationships on one foundation.
Compare
What exists? What should exist?
Determine what is needed
Matrix · policy · legal requirements
Coordinate the next steps
Checks · tasks · approvals · actions
Execution ↔ feedback
Your people and tools
Microsoft Intune
For example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Start with one integration, register or check. Build on the same data and rules.
Combine into one controlled process
Data → rules → execution
Combine
Inventory + CMDB + ownership
Determine & check
Match, compare and review discrepancies
Execute & report back
Update CMDB · Create service ticket · Review replacement or retirement
Check sources and rules, test changes and track the outcome. Manual tasks get an owner and confirmation.
Build visually. Manage easily.
Reuse building blocks, adapt your process and test the change. Manage it yourself, together with us or let Scope4mation take care of it.
From product to process
How to use the integration
Assets → CMDB
Synchronise agreed device fields with your CMDB, for example TOPdesk or ServiceNow.
Software & licences
Compare available software and usage information with records and initiate review where needed.
IT asset lifecycle
Compare inventory with operational records and initiate checks for reassignment, replacement or retirement.
Connect work across your applications
What would you like to connect Lansweeper with?
Choose the role in your workflow. Explore applications from the scenarios and further directions to discuss together. We define the data, actions and available interface for each combination.
Start with one use case. Connect customer, employee and asset data, for example, and agree which source is authoritative. Reuse those relationships, a matrix where needed and configured actions in the next workflow. Agree who maintains the data and rules. Expand without repeatedly connecting and maintaining the same information.
A replacement laptop without losing context.
An employee receives a replacement device. The old asset, new record and open service or security tickets must remain connected.
Combine
Use the central relationship between owner and device identifiers. Combine handover, technical inventory and return with existing tickets.
The outcome determines what follows
Receipt confirmed: update ownership and relationships. Old device missing or uncertain match: start a targeted review instead of overwriting historical records.
The benefit
Current records and a traceable handover even when a management tool uses different names.
A different name does not mean a new record.
A person or organisation has a different name in the source than at a customer or supplier. Matching text again can create incorrect or duplicate relationships.
Combine
Retain verified identifiers and source rules in a shared table. Reuse the relationship for requests, tickets and other integrations.
The outcome determines what follows
Known key: use the relationship. Multiple candidates or a missing identifier: request review. Once confirmed, reuse the established relationship.
The benefit
A consistent data foundation managed by your team instead of investigated again for every connection.
Ordered, delivered and actually in use?
Procurement, a supplier and technical inventory each hold part of the picture. A delivered asset is not automatically assigned to its correct owner.
Combine
Compare orders, delivery details, serial numbers and inventory with central ownership relationships. Keep missing confirmations part of the workflow.
The outcome determines what follows
Matching data: update the agreed records. Unknown device, unexpected owner or unconfirmed delivery: create work for the correct support group.
The benefit
Fewer gaps between administrative and technical records and targeted follow-up of discrepancies.
Your process needs more than a standard action?
Configure the missing API request, input and output in API Composer. Use its response in the next step and combine it with data tables, forms and automations. Extend the same product and reuse the configured building blocks.
Use Service Automation Suite to update a ticket in TOPdesk, for example, with fields available through its API, such as category, priority, status and support group. For another application, configure its request and field mapping. The outcome determines the next action: confirm, add information or request review, not merely check whether the request arrived.
Need to publish data or let others submit it? Endpoint Composer exposes a configured Service Automation Suite data object with selected methods and security profiles. Other building blocks handle subsequent processing.
From product to workflow
Lansweeper in your workflow
Pull up a chair. Or join us online.
Over coffee, tea or online: tell us what you are working on.
We can help with the integrations, automation and coordination your process needs, even if your application is not listed yet.
Microsoft Intune
