Feature Requests

Allow API queries by serial number or any data inside an integration, or manually created card. Use Case: Query a system by serial number or any field data using the API.

We want the ability to automatically generate process steps based on assets created within a specific Asset Layout. This would allow for automation when setting up workstations or other repeatable processes, reducing manual input and ensuring consistency. Feature Requirements: Toggleable Setting – Enable or disable this automation per client. Selection Menu – Choose which Asset Layouts will trigger process creation. Process Selection – Ability to map Asset Layouts to specific processes. Flow Overview: Step 1: Create an asset within a selected Asset Layout. Step 2: The asset’s fields become steps in a process checklist. Step 3: Technicians can check off each step as they complete them.

We'd love to be able to add/remove QuickNotes from the API for allowing us to automate various client alerts.

Currently the expirations API only provides a GET method. It would be amazing to be able to PUT/POST/DELETE expirations for each asset type via this API.

It would be useful to have the ability to set group permissions via the API, retrieve and set password folder permissions via the API, and set user roles via the API. In general, having API access to retrieve, update, and post any available permissions for items in Hudu would streamline setup and configuration for advanced users.

When exporting list data, you receive a special JSON format and an ID rather than the actual list option names. Current Behavior: Asset Layout Name: Computers List Name: Computer Models List Options: A, B, C, D Instead of showing the list option names in the export (e.g., A, B, C, or D), the CSV exports the field in a JSON-like format: {"list_ids":[1]} This makes it difficult to interpret the actual selected values. Desired Behavior: The CSV export should show the actual list option names (A, B, C, or D) instead of just the list option IDs in a special format. This would improve usability and make the exported data easier to read and work with. Let me know if you need further clarification!

As of right now, you can either delete All cards from integration, all integrated assets, the integration entirely, or individually delete HaloPSA cards. It would be great if this was more fleshed out to include options such as: Only delete HaloPSA assets associated with a specific asset group Only delete HaloPSA assets associated with a specific client Delete HaloPSA assets that don't have manually added data Having a DELETE request function through the API for cards

Typically, a method like GET /api/v1/companies would have a querystring value like "showArchived=true" to allow API users to query for archived clients. This would be useful for programatically un-archiving, since there doesn't appear to be another way to get the Hudu company ID's of archived clients by company name. For example, right now - I'm working on an onboarding automation and this is causing hangups when companies return after leaving or when being upgraded from an old package to one that uses the new automated onboarding procedure. Since I can't retrieve their old Hudu ID, and their name is already taken, I can't automatically make the company available for our support staff in Hudu.

Allowing us to change the background of custom magic dashes in Hudu would be awesome. Currently there is no way to set a web image as full size background.