We are a heavy user of N-Central, utilizing nearly everything the platform offers — from RMM, monitoring, topology, automation, patching, and policy management — except for AV, EDR, and Backup (as those are centralized to Check Point and Veeam).
Unfortunately, Hudu’s current N-Central integration exposes only a small fraction of what N-Central can actually provide.
Our goal is to leverage Hudu as the documentation and visibility layer above N-Central’s operational data — without needing multiple redundant tools like Auvik, Domotz, or Watchman.
To make this possible, the integration should be expanded to utilize the full potential of N-Central’s API data and classification logic.
⸻
Current integration capabilities (summary)
Hudu currently:
• Imports Customers, Sites, and Devices from N-Central.• Correctly recognizes device types (Servers, Workstations, Printers, Routers, Switches, etc.) and links them to the proper asset layouts when configured.• Supports “Detailed device info” for extended hardware data (CPU, RAM, OS, etc.) but in very misserable way.These features work well as a foundation — but the integration stops there.
Hudu does not yet use or display the full richness of N-Central’s data, such as probes, network relationships, monitoring states, user mappings, or software inventories.
⸻
Requested improvements
Enhanced data depth and enrichment
• Import all available hardware and OS metadata (serial, firmware, BIOS, storage, NICs, uptime, etc.).
• Include probe devices and identify them clearly (“Site Probe / Monitoring Node”).
• Bring in device group, role, and custom properties
• Sync last logged-in user and automatically link it to the user/contact in Hudu.
Network and topology visibility
• Sync and visualize probe-discovered topology (connections, VLANs, subnets, bandwidth metrics).
• Include interface-level status and metrics (up/down, speed, utilization, errors).
• Optionally generate a topology map inside Hudu linking assets by their actual physical or logical network relationships.
Monitoring state and flags
• Sync device health status (Online, Warning, Critical, Down) and optionally auto-update Hudu Flags:
• Offline → Critical
• Patch failed → Outdated
• AV disabled → Needs Review
• Allow workflow triggers in Hudu based on these status changes (e.g., create review tasks automatically).
Policy linkage and automation
• Automatically attach relevant policy-type assets to devices based on N-Central role or tag (e.g., “Server Policy” → all server assets).
• Allow policies to be updated dynamically if a device moves sites or roles change.
• Sync review and ownership metadata for policy accountability.
Software inventory
• Import installed software lists from N-Central per device.
• Link recognized applications to existing Software assets in Hudu.
• Provide both perspectives:
• From software → see all devices where installed.
• From device → see all installed applications.
Alerts, Secure Score, and health data
• Display active alerts, warnings, and event summaries from N-Central.
• Show Microsoft Secure Score and Defender/EDR posture when available.
• Enable configurable thresholds for Hudu flag automation or dashboard alerts.
Probe and site health
• Show site-level summaries (availability %, device count, active alerts) based on probe data.
• Integrate into the customer overview as a clear health indicator for each environment.
Improved linking and actions
• Add deep links from Hudu devices/customers directly into their N-Central counterparts.
• Show real-time agent status and, where possible, include quick actions (Remote Control, Reboot, Background Tools).
Synchronization and transparency
• Allow flexible sync intervals (30 min–6 h).
• Provide clear sync logs, timestamps, and result summaries.
• Warn admins when authentication fails or N-Central tokens expire.
⸻
Why this matters
N-Central is a complete MSP operations backbone — monitoring, automation, patching, and topology in one platform.
Hudu already integrates with it at a basic level, but it should act as the documentation, compliance, and process intelligence layer above it.
A deeper integration would:
• Eliminate redundant monitoring tools.• Keep documentation automatically accurate and alive.• Connect technical data (from N-Central) with operational knowledge (in Hudu).• Allow teams to see infrastructure health, policies, and processes in one place.⸻
In short
We’re requesting that Hudu expand its N-Central integration to fully utilize all available API data — probes, network topology, health, software, and user mappings — while maintaining the existing device-type linking.
This would make N-Central + Hudu a truly unified MSP ecosystem for:
Monitoring, Documentation, Automation, and Compliance — all connected, always current.