RMM-to-Documentation Pipeline
Turning live RMM device inventory into per-site network documentation in IT Glue, anchored on each network's gateway.
context
An MSP managing networks for roughly 25 client organizations, with NinjaOne as the RMM watching every managed device and IT Glue as the documentation system technicians actually consult. Network documentation - what is at this site, what is the gateway, what sits behind it - was maintained by hand, which means it was accurate on the day someone wrote it and drifting every day after.
problem
The RMM already knows the ground truth, but as a flat device list per organization - accurate and unstructured. Documentation needs the opposite shape: per-site pages with the network laid out. The gap between those two shapes is exactly the work nobody has time to keep doing by hand, so the pipeline's job was to derive the structure from the inventory instead of asking a technician to re-type it.
constraints
The RMM's data model has organizations and devices, not sites and topology - the structure documentation needs is not stored anywhere and has to be inferred. Many clients span multiple physical sites, and a device documented under the wrong site is worse than an undocumented one. And the pipeline had to be safely re-runnable on demand, refreshing what is already in IT Glue rather than piling up duplicates on every run.
approach
PowerShell against the NinjaOne API pulls the device inventory, then applies gateway-first site detection: identify each network's gateway device first, and the devices behind that gateway define the site. The gateway anchors the structure - find it, and the rest of the site assembles around it. The structured result is written into IT Glue through its API as per-site network documentation. A technician runs the pipeline on demand, so the documentation reflects the live network as of the last refresh instead of the last time someone edited a page.
outcome
Per-site network documentation across the managed portfolio, generated from live RMM inventory instead of maintained by hand. A technician walking into an unfamiliar site gets the gateway, the networks, and what sits behind them from documentation that was derived from the network itself.