Most organizations have some type of endpoint management tool such as JAMF, MECM (or SCCM), Intune, Munki or Kandji for macOS & Windows. These systems typically allow end users to browse and install configuration profiles, applications, and run pre-built scripts on their machines.
The Moveworks bot connects users to these systems by providing them with “deep links” that take them to the specific application/policy/package that they are asking for.
There are two use cases that leverage the deep link functionality:
There are 2 ways to find deep links for JAMF offerings:
A JAMF admin can extract all deep links for JAMF offerings via Postman or the interactive API Explorer when logged in via an administrator account:
https://<JAMF Instance Name>:<Port Number (usually 8443)>/classicapi/doc/#/policies/findPolicies
The output will be an XML file that can be converted into a CSV to view the policy IDs for all apps.
You can also grab the IDs of the self-service policy packages manually by tailing the JAMF log file on a device while the policy is executing by following the instructions below:
tail -20 /var/log/jamf.logRepeat this process for every single self service app you want to add to the bot, at the end you will have
selfservice://content?entity=policy&id=<ID_NUMBER>&action=viewselfservice://content?entity=policy&id=<ID_NUMBER>&action=execsoftwarecenter:SoftwareID=ScopeId_<software_package_id>
You can programmatically extract all Intune links using the MS Graph API via the DeviceManagementApps.Read.All permission applied to the bot’s App ID in Azure (this should be included in the Teams bot installation if your organization will use Moveworks within Teams). Use this API call to extract the links.
Link format for Intune
You can also build this out as an Agentic Plugin.
If you use the Flexera App Portal as a service portal front end to request access to applications, you can find the packageID - the software that gets deployed to the machine - when you click on a software from the portal and look at the URL. Clicking on the URL, will take the user to the right page to look at the software where all they need to do is add to cart and checkout the app. Then Flexera system will deploy it onto their machine via another system (JAMF, Altiris, etc.) You can look through the Flexera Admin Guide here for additional details: https://docs.flexera.com/appportal/AppPortalAppBroker2019r1AdminGuide.pdf
Link format for Flexera App Portal 2015 R2 (10.0.7.0)
Unfortunately, Broadcom Altiris (FKA Symantec Altiris) does not have the functionality to deep link to a specific software in the portal. You can only deep link to the portal directly, and then provide instructions to the user on what to search.
View Setting: Clicking this detail link takes the user to the correct self service item within Munki and will require one step of user confirmation before installing the package.
munki://detail-<item_name>
Note that item_name is the pkginfo name key and not the display name. Detail links are case sensitive.
For example: munki://detail-AdobeReaderDC
For more information on Munki links, see here:https://github.com/munki/munki/wiki/Munki-Links
To grab the links for each Self-Service software items in your Kandji:
Share... buttonCopy link button to copy the deep link for that software item.
Link format for Kandji