Integrations

I see that the JSON response includes a ninjarmm_id. It would be helpful if this ID could be used to automatically merge assets when importing from Halo, to prevent duplicates and streamline asset management.

Currently, The HaloPSA integration pulls in devices and uses the "Inventory Number" as the Hudu Asset name. The "Device Name" would be way more useful.

Please add the ability to skip importing contacts in Atera

I would like to see Hudu pull in the new Ninja Warranty data in Ninja v6 and v5.9.

Would be nice if there was a launch URL back to the HaloPSA asset. We store passwords in HaloPSA and the assets sync over to Hudu, however the passwords fields do not sync decoded so we have to open the asset in HaloPSA to retrieve the password. There are also other assets we need access to from within Hudu and the Launch link would be awesome. This is similar functionality that currently exists for the NinjaRMM integration.

I would like to see Hudu sync ConnectWise Manage company contacts from CIPP or Liongard M365 integration.

Add the ability to 'delete card' or 'delete entire asset' for each primary integration mapping (contacts, locations, primary sync location), and for each mapping sort rule you might have. Example 1: delete the entire asset for all assets created by the sync for the default contacts mapping. Example 2: delete the card from all assets for a sort rule you created. In more detail: Scenario: You are syncing all "Cat" configurations in Manage to the "Animals" asset layout in Hudu. Now, you've determined that cats deserve their own asset layout in Hudu and created one named "PSA Cats." Unfortunately, 300 cats have already been synced and won't get moved to the new asset mapping unless they are deleted. They're pretty pissed off about it. Fun aside, the only option here is to delete each 'entire asset' from the PSA sync overview... one... by... one. You might have other valid assets using the target layout, so blanket deleting all assets of that type won't work.

E.G. Currently Logged in user, make, model, etc. This way we can add this to the lists view, so all devices can be tracked against signed in users.

The current N-Central integration imports companies, locations, and devices into Hudu, but there are several usability and data management issues: 1. Device-to-Location/User Linking Missing: Although locations and devices are imported, devices are not automatically linked to their respective locations or users. Ideally, devices should be matched to users based on username or other identifiable attributes and assigned to their correct location automatically. 2. Excessive Data Import (“Data Vomit”): Enabling the “Import all device data” option results in an overwhelming amount of unstructured information being pulled into Hudu. This significantly impacts clarity and usefulness of the imported data. 3. Lack of Field Mapping: It would be highly beneficial to allow mapping N-Central fields to existing Hudu asset fields. This way, only relevant information is populated into the appropriate places, instead of dumping all raw data into the asset record. Suggested Enhancements: • Allow mapping of specific N-Central fields to Hudu asset fields. • Provide filtering options to choose which fields to import. • Automatically link devices to users based on username/email. • Automatically assign devices to the correct location based on imported location data. These improvements would drastically enhance the usability of the integration and reduce unnecessary manual cleanup work.

Right now, when AutoTask contacts are synchronized into Hudu, there is no way for the Primary Contact to be indicated. There is a field in AutoTask that indicates if a contact is the primary, and there is one in Hudu, but there is no relation between the two.