Please check existing posts to see if your feature request already exists.
🐛 If you’ve encountered a bug, please submit a ticket to the Hudu support team to ensure a quick response.
Have a feature idea or feedback on how we can improve Hudu?
UniFi OS: support client consoles where you're an admin but not the owner
MSPs are usually invited as admins on their clients' UniFi consoles rather than owning them outright. Today the UniFi OS integration needs a key from the console owner, so those client consoles sync sites but never pull in devices. The ask is for a way to document device inventory using an admin-level key, even if that means bringing over less data than a full sync does. Getting the devices in is the main thing. Requiring the client's owner account isn't practical for most MSP relationships, and asking clients to hand over owner credentials is a non-starter.
Unifi OS SSID
Requesting SSID sync support, specifically: - Sync each SSID per site into a chosen asset layout, with an Asset Layouts option similar to the existing device categories - Include SSID name, security type, linked network/VLAN, band, enabled status, and guest flag - Optionally store the WiFi passphrase as a linked Hudu Password - Relate each SSID to its network in IPAM and to the access points broadcasting it
Extend ManageEngine Endpoint Central integration to on-premise and MSP editions
The new ManageEngine Endpoint Central integration (Hudu 2.45) currently supports only Endpoint Central Cloud. The setup requires a Data Center region, Client ID and Client Secret, and there is no option to enter a custom server URL. This excludes all on-premise Endpoint Central installations. In addition, the documentation does not state whether the integration supports Endpoint Central MSP, or only single-tenant Endpoint Central. Requested changes: On-premise support Allow a custom server URL including port (for example https://ec.example.com:8041 for Endpoint Central MSP, or https://ec.example.com:8383 for Endpoint Central) Support authentication with an API token generated in the on-premise console Endpoint Central MSP support (cloud and on-premise) Map each MSP customer to a Hudu company through Match Companies Sync devices per customer, using the existing sort rules and Connected Fields Documentation clarity State clearly which editions and deployment models are supported: Cloud vs On-Premise, and Endpoint Central vs Endpoint Central MSP The Troubleshooting section refers to a server URL, but the setup has no such field. This should be aligned. Why this matters: Endpoint Central MSP is ManageEngine's dedicated product for MSPs. Its multi-customer structure maps directly to Hudu companies. Many MSPs run Endpoint Central on-premise for security, compliance and data sovereignty reasons, and currently cannot use the native integration at all.
Integration with Aruba Central
We are currently with Meraki but looking at moving 200 sites to Aruba, however no integration exists to sync switches/APs with Aruba Central.
Website Import from Connectwise
When linking the Connectwise Integration, Hudu should at the very least pull the url from every client and automatically populate the url in their website section, not just their dash.
ConnectWise Location to Sub Company
We have some clients who are very complex multi-location businesses. We would like all of the data for configurations we have in ConnectWise PSA to instead of syncing to one parent site to be able to be split into sub-companies to easily see the data. We would then sync other integrations such as Auvik and Unifi to those companies to always keep data updated.
Extend N-Central Connected Fields
Serial number, manufacturer, IP address, and model are all fields that need to be included for connected fields with the N-Central integration. This allows technicians to reference them directly in the table view for a quick glance, saving time and eliminating the need to click into each asset and search manually.
Sync projects from ConnectWise into Hudu
Problem: MSPs manage projects in ConnectWise but Hudu has no way to pull that data in, so projects get manually duplicated or skipped in documentation. Request: Sync ConnectWise project records (name, status, company, dates) into Hudu, mapped to the right company.
NinjaOne - Match devices Based On Primary Serial Number
Several integrations offer the ability to match assets based on serial number. Please enable this option for the NinjaOne integration.
Halo KB sync - edit FAQ lists
We have a FAQ list in Halo for KBs we publish to the Halo Client Portal. Because the documents synced from Hudu are un-editable we can't publish them, and have to keep a separate store of KBs edited and maintained in Halo. I'm not too sure how you would fix this without marking the KB as editable, but it would be good to have.
Add Warranty Expiration Field to Halo integration
Halo date fields (including warranty expiration) come into Hudu as text through Connected Fields, so they can't be mapped to a Hudu Date field or added to Expirations. Would love to see Date field type support added for Halo connected fields so warranty and other date data can populate expirations automatically.
Integrate with Apple Business Manager
It would be great to be able to sync our Apple device data to Hudu.
Automatically sync profile pictures from JIT provisioning
Please allow JIT to automatically pull and update user profile images from the origin account.
Integration Request for Slide BCDR
We're beginning to use Hudu for our MSP's documentation and we'd love the ability to Integrate Slide BCDR (Project Orca) to automatically pull backup info into Hudu.
MCP Server to allow read access to Password Assets
We have Claude creating QBR reports for us and data sources like Barracuda, Unifi, and Infima do not have published MCPs so we need to use API keys, these keys can be used in a session per session basis however to be secure it would be helpful if Claude to use the Hudu MCP to look into the API keys we have stored in password assets. To protect all other PW assets maybe this can be restricted to a password folder so its not all passwords. I could create and API folder and dump the PW assets into it, then train Claude to look there for access when it needs it. This would be a huge win for us until more companies release MCPs.
Spiceworks Inventory
We've got a small service desk using Spiceworks for ticketing and inventory. I've been CSV exporting the Spiceworks computer Inventory and importing it into Hudu, but I'd be awesome to have an integration that that could do this.
Multiple NinjaOne Environments
We would like to see the capability for this integration, and all integrations, to be able to have multiple tenants or environments connected to them. For example, I want to connect 4 NinjaOne environments to my Hudu instance.
Native integration with DocBee (German PSA/ticketing system)
Please consider adding a native integration for DocBee (docbee.com), a PSA and ticketing platform that is widely used by MSPs and IT service providers in Germany and the DACH region. DocBee offers a full REST API (tickets, time entries/services, customers, contacts), so the technical foundation for an integration is already in place. Ideally, the integration would work similarly to the existing NinjaOne integration: matching DocBee customers to Hudu companies, displaying open tickets per company (e.g. via Magic Dash or cards), and deep-linking back into the DocBee portal. We currently solve this with a custom script via both REST APIs, but a native, officially supported integration would benefit the growing number of Hudu users in the German-speaking market, where DocBee is a common PSA choice.
Exclude Archived KB from HaloPSA Sync
Currently, archived KB articles are still synced to HaloPSA, and we need to manually disable them after each sync. This creates extra manual work and increases the risk of outdated or archived documentation becoming visible or available in HaloPSA when it should no longer be used. Ideally, Hudu would provide a setting that allows archived Global KBs and Client KBs to be excluded from the HaloPSA sync automatically. This would help keep the HaloPSA knowledge base cleaner, reduce manual cleanup, and prevent archived documentation from being exposed unintentionally.
HaloPSA company sites/child companies - Sync to Hudu as companies
Currently, sites in Halo are imported as assets through the integration. It would be great to have a way to treat these as separate child companies to the existing parent company.