Software & licences
Compare available software and usage information with records and initiate review where needed.
All integrations
Devices & inventory
Snow License Manager provides visibility into software installations, usage and licences. Explore how Service Automation Suite can compare available data with employees, devices and your policies. Route unused software or discrepancies for review and follow-up, for example through a TOPdesk task. Available interfaces, versions, licensing and permissions determine the implementation; this is not a claim of a prebuilt Service Automation Suite connector.
From product to process
How to use the integration
Assets → CMDB
Synchronise agreed device fields with your CMDB, for example TOPdesk or ServiceNow.
Exceptions → tasks
Route missing information or discrepancies to the team responsible for follow-up.
Combine into one controlled process
Data → rules → execution-
Combine
Software usage + licence + employee
-
Determine & check
Compare against licence rules and policy
-
Execute & report back
Review discrepancy · Start reassignment task · Update record
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.
More process examples & technical details
The work between your applications
Records updated.
Do they match reality?
Service Automation Suite connects Snow License Manager 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 IntuneFor example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Maintain records
Software in use. Does the licence still fit?
Snow License Manager provides visibility into software installations, usage and licences. Explore how Service Automation Suite can compare available data with employees, devices and your policies. Route unused software or discrepancies for review and follow-up, for example through a TOPdesk task.
Available interfaces, versions, licensing and permissions determine the implementation; this is not a claim of a prebuilt Service Automation Suite connector.
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.
Relevant data or workflow status
Microsoft Entra IDUpdate, execute and record outcomes
Read usage and licence data
Identify the software, usage and licence data available from your Snow environment. Validate interfaces, version, licensing and permissions first.
Compare against your rules
Compare available data with employees, devices, roles and policies. Present discrepancies or potentially unused software to the responsible person; do not revoke access automatically based on a usage measurement alone.
Follow up and check again
After approval, start the agreed task, for example in TOPdesk. Record the outcome and check the next measurement to see whether records and usage align. Validate supported actions before implementation.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect Snow License Manager to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Example configuration · shaped by your process
Compare inventory and maintain ownership
Connect and test
API ComposerChoose the API method, URL and authentication. Manage the host and credentials in an environment. Test a request in Discovery and inspect the fields actually returned by the API.
Combine and compare
Data Flow ComposerSelect fields, translate codes and relate records using shared data. Compare source and target to identify new, changed or incomplete records.
Execute and use the response
API ComposerBuild the request body from validated data and inspect Body Preview before testing. Use the result ID in Data Context for the next request or save output to an entity. Configure write-back separately.
Recognise errors and follow up deliberately
API ComposerConfigure error rules by HTTP code and/or message. A temporary API failure can use bounded retries. A missing relationship or rejection needs another route: record the cause and configure a verification task for the appropriate team, for example.
Which data do you maintain?
An example configuration, not fixed field names or a mandatory combination.
- Serial number and device ID
- Record which identifiers refer to the same asset and reuse that relationship in other integrations.
- User, owner and administrative status
- Combine inventory with handover and supplier data. A signed-in user is not automatically the registered owner.
- Discrepancy and confirmed update
- Update the agreed record or create a targeted verification task, for example in TOPdesk. Retain the result reference.
Sent ≠ processed. Use the response and agreed validation to determine the next step.
Need to publish data yourself?
Use Endpoint Composer to publish a configured Service Automation Suite data object. Choose read and write methods and security profiles so a customer can retrieve agreed service data or a supplier can submit information, for example. Configure data selection and subsequent processing separately.
Endpoint ComposerFrom data to a complete process?
Combine the integration with a form, a shared matrix, a review or collaboration between service teams. For example, an approved request leads to execution in Microsoft Entra, a ValidSign signature request and feedback in TOPdesk. Your process determines the steps needed; not every use case requires all these components.
Explore the connected building blocksBeyond the first integration.
Use the same data and rules in your next process.
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.
Build it yourself: explore the technical approachNeed 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
Snow License Manager 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.
