Can custom script output be retrieved using the Hexnode MDM API?Solved

Hi @hugo_l ,

Hexnode supports storing custom script output in a Custom Attribute. For macOS, Windows, and Linux, you can map the output of an executed custom script to a selected Custom Attribute and view the captured value under Device Info > Custom Attributes.

However, the current Hexnode API documentation does not provide an endpoint for retrieving custom script execution output or reading the value stored in a device’s Custom Attribute. So while Custom Attributes can be used to store and view the script result in Hexnode, they cannot currently be used to retrieve that result through the Hexnode API.

Regards,
Isabel Lora
Hexnode UEM

@hugo_I @isabel_lora
I created an account to mention that this feature would be incredibly important for me.

There are some user applications which are not discovered by the Hexnode agent something that someone installed with brew for example.

If I wanted to go query my entire fleet and report on which version of this brew application was installed on my devices it would be incredible to save this data as a custom attribute and query it with the API.

Additionally I’d likely need to run automations if some version of this application is below a threshold. Either way I just wanted to note the importance of this workflow. Automations really depends on our ability to extend and make use of the the API.

Hi @jworkman ,

Thanks for sharing your suggestion! I understand the need for this functionality and how it could be useful. I’ll share your suggestion with the team as a feature request. Please keep an eye on the Hexnode UEM release notes for announcements about new features and enhancements.

Regards,
Isabel Lora
Hexnode UEM