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.
The new Huntress integration create identity objects using the email address rather than attempting to match an existing object that contains the email address. Since we migrated from IT Glue our roughly 20k identities are created using the actual name of the user. Different matching options would make this more usable.
The new Huntress integration allows syncing of agents, but it assumes all agents will the same asset type in Hudu. We currently distinguish between user endpoint and servers. Is it possible to allow more elaborate mapping?
Are there plans and a roadmap to bring in more device details from ConnectWise RMM (Asio)? The current integration syncs companies, sites as locations, and devices, but the device data is limited. To fill the gap, I currently run a PowerShell script that pulls data from the ConnectWise RMM API and pushes it into Hudu. I would like the native integration to handle this so I can retire the script. Device details I would like synced: Hardware: manufacturer, model, serial number, CPU, memory, and storage. Operating system: OS name, version, and build. Network: IP addresses, MAC addresses, and domain. Status: last check-in, online status, and last logged-in user. Patch status: available and installed patches. Installed software inventory. These details are available through the ConnectWise Platform API: GET /api/platform/v1/device/endpoints GET /api/platform/v1/device/endpoints/{endpoint_id} GET /api/platform/v1/patching/{endpoint_id}/patches Having this data synced natively would keep our device documentation accurate without custom scripting, bring the ConnectWise RMM integration in line with other RMM integrations in Hudu, and make the connected fields far more useful.
The ConnectWise RMM integration currently populates a combined “Make & Model” field. It would be helpful to split this into two separate fields, Make and Model, for cleaner organization and reporting. During that transition, there should be an option to hide the existing combined field while temporarily retaining its data, making it easy to compare and identify which assets aren’t being populated through CW RMM. This would require support for hiding asset layout fields without data loss, along with the ability for the CW RMM integration to sync make and model to individual fields.
Devices in NinjaOne often have more than one network adapter, each with its own IP and MAC address. The NinjaOne connected field for IP address only brings in one address, and there is no way to choose which one or to bring in more than one. We would like to be able to sync every IP and MAC address on a device, or at least choose which adapter each connected field uses. This would make network documentation more accurate and would save teams from filling these in by hand or with their own scripts.
Many teams use NinjaOne checkboxes to track things like server roles (file server, DNS, print server and so on). Today each NinjaOne field can only be connected to a single text or rich text field in Hudu. To show these as one tidy list on an asset, you have to build your own script. We would like to select several NinjaOne checkbox fields and have Hudu combine the ones set to yes into a single field on the asset, such as a list. For example, an asset would show “File server, DNS, Print server” instead of a separate checkbox for every role. This keeps asset pages shorter and easier to read, and it saves teams from maintaining their own sync scripts.
Native integrations currently re-sync on a fixed platform-wide interval (roughly every 3-4 hours), and admins have no control over how often or when that happens; the only option for fresher data is a manual re-sync. We'd like admins to be able to set the sync interval per integration and/or schedule syncs for specific times of day. Customers who rely on near-current data, such as RMM device inventory, end up re-syncing manually to fill the gap, while others may prefer syncs to run at predictable times, like outside business hours.
today you are pulling in all the networks to IPAM through the integration but not adding the VLAN to it. Might be related to this UniFi network config add vlan to networks IPAM overview - Hudu but thats for the old integration i believe. Also a side note, saw that “UDM Pro Max” was tagged as a “switching” but that might be UI API issue, so it got added to the switches instead of gateways.
Proposed solution Pull SNMP-derived inventory for NMS devices from NinjaOne, including manufacturer, model, serial number, and firmware, when they aren’t available under system. Add a firmware Connected Field for NinjaOne devices. Allow Custom SNMP monitoring attributes (custom OIDs) to be mapped to Hudu asset layout fields, similar to how NinjaOne Custom Fields can be mapped today. Show these values on the NinjaOne card for NMS devices.
I would like CW RMM sites to use matching logic similar to that of companies. Please allow CW RMM sites to be matched to existing Hudu companies using logic similar to company matching.
Current behavior: Asset layout fields can be mapped to six Intune data points, all device-level. No user-level data is available. Requested: 1. Add these managedDevice properties as integration data points: - userPrincipalName - userDisplayName - emailAddress - enrolledDateTime - lastSyncDateTime 2. Allow Asset link fields to be integration-mapped, so a device can auto-link to the People asset whose email matches the device's userPrincipalName. Why: Device-to-user mapping is core MSP documentation. Today it requires a manual field or an external script hitting the Hudu API, which defeats the purpose of the native integration. Environment: Hudu Cloud, Microsoft Intune integration, custom "Intune Devices" asset layout.
On the Intune integration, allow a layout to be chosen per operating system, with the existing default used when an operating system has no mapping. iOS devices sync into the Mobile Devices asset layout. Windows and macOS computers sync into the Workstations asset layout. Any operating system left unmapped continues to use the current default layout. The mapping is available per company integration, since Intune is set up per company. New devices follow the mapping. Existing devices stay where they are unless the user explicitly chooses to re-home them.
It would be great if we could get an integration between PDQ Connect and Hudu to sync assets like Syncro or other RMMs
Please add an option to automatically create a support ticket in a connected ticketing system, such as Atera, when a Hudu process/SOP task is assigned to a technician. Currently, assigning work in Hudu means we also need to manually create a ticket to get it into the technician’s normal work queue. This duplicates administration and creates a risk that assigned tasks are overlooked. Ideally, this feature would: Create a ticket against the matching customer and assign it to the corresponding technician. Include the task title, description, due date, priority, and a link back to the Hudu task. Display the ticket number and link within Hudu. Prevent duplicate tickets when a task is updated or reassigned. Be optional, so we can choose which processes or tasks create tickets. This would connect SOP assignments directly to technicians’ daily ticket queues, making work easier to track and reducing manual data entry.
The Huntress integration currently syncs all agents into the single asset layout I choose. There is no sort rule to place agents into different asset layouts based on an attribute, as other integrations allow. As a result, servers, workstations, and Macs all land in one layout, creating duplicates of devices already documented in other layouts. I would like sort rules for Huntress agents so each agent is placed in the correct asset layout based on reliable data exposed by the Huntress API.
Integrations show more synced fields on an asset than can be mapped to a layout field. For example, the Meraki card on a firewall shows Mac, Name, Model, Serial, WAN1 IP, WAN2 IP, Address, Firmware, latitude, longitude and Configuration Last Updated At. When setting the Integration data point on a text field, the only choices are device_display_name, device_ip_address, device_mac_address, device_model, device_serial_number and device_type. Make every field an integration syncs available as an integration data point. Example: map Meraki Firmware to a Firmware Version field, and WAN1 / WAN2 IP to public IP fields, so they stay current instead of being typed in by hand. Apply the same to other integrations' synced fields.
The Microsoft 365 / Entra integration syncs name, mail, given name, UPN, office location, business phones, mobile phone, job title and mailbox details. Please add these Entra ID user attributes: Company Name: separates staff from contractors and vendor accounts, such as MSP engineers. Department: shows which team a user belongs to. Manager: shows who approves the user's access. On-Premises Sync Enabled: shows whether the account is mastered in Active Directory or cloud-only, which changes how it is disabled or renamed.
In Claude, every Hudu MCP connector tool shows under "Other tools" instead of being classified as a read or write tool. Our organization does not allow "Always allow" for write tools, and "Other tools" are treated the same way, so someone has to approve every call, including simple lookups. Set MCP tool annotations on each tool: readOnlyHint true on tools that only read (index, show, search and similar). Set readOnlyHint false, with destructiveHint where appropriate, on tools that create, edit, archive or delete.
Currently primary serial is defined by integration cards. Please allow an option to match to an existing asset layout field.
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