Macs, iPads and iPhones belong in the same asset workflow as other devices. Explore connecting available Jamf Pro inventory to your service desk or CMDB, such as TOPdesk, and to HR and supplier data through Service Automation Suite. Government and healthcare teams can follow up missing records, unclear ownership and returns, including shared departmental devices.
The work between your applications
Apple management connected to assets and employees.
Macs, iPads and iPhones belong in the same asset workflow as other devices. Explore connecting available Jamf Pro inventory to your service desk or CMDB, such as TOPdesk, and to HR and supplier data through Service Automation Suite. Government and healthcare teams can follow up missing records, unclear ownership and returns, including shared departmental devices.
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
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.
Apple & assets Popular
The iPad has arrived. Is it correctly managed?
A care department receives shared iPads; a municipality issues Macs to employees. Service Automation Suite can compare deliveries and Jamf observations with your asset records, for example in TOPdesk, and route exceptions for review.
Service Automation Suite · Central coordination
Match, compare and follow up
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Source & context
Apple & assets
For example, connected to
Microsoft Intune
Records, review and confirmation
Match the same device
Link serial number and Jamf ID to the existing asset in your CMDB or service desk, such as TOPdesk. Use HR for employee relationships and assign shared iPads to a team or location rather than automatically to the last signed-in user.
Compare delivery with management observations
Check whether delivered devices appear in Jamf and assigned assets are still observed. Account for stock, offline devices and inventory age.
Resolve the discrepancy
Create a targeted activity in your service desk, such as TOPdesk, for missing enrolment, incorrect location or return. Have an operator confirm the outcome; missing telemetry does not automatically trigger erasure or write-off.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect Jamf Pro to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Agree access and application scope
Jamf documents computer and mobile-device inventory. Validate supported API versions and read permissions per environment; older endpoints may be deprecated. Inventory is a timestamped observation, not proof of handover or return. MDM commands and erasure require a separately approved configuration. This is an integration scenario, not a pre-tested Service Automation Suite connector.
Choose 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.
Build 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.
Configure 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.
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.
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.
Build on the same foundation
More with Jamf Pro
Company assets
From delivery and handover to management and returns. Connect records to what management tools actually observe.
Microsoft Intune
