Connect intended state and discovered fleet data.
Synchronize mapped device and site properties between Gluware and NetBox, with configurable property ownership, linking rules, exclusions, and schedules.
WHY IT MATTERS
The source of truth and the observed network need to work together.
Intended state in NetBox and discovered state in the network serve different purposes. When they are connected through manual reconciliation, automation can depend on information that has not been brought into the operating process. The Gluware integration connects those responsibilities without treating NetBox as the device execution layer.
WHAT NETBOX INTEGRATION PROVIDES
Capabilities built for the work.
Define record linking and mappings
Match devices between the systems and map properties, roles, types, sites, and supported custom fields. Configure how unmatched records are handled.
Set ownership and sync direction
Define which system supplies each mapped property. Bring NetBox-managed data into Gluware or update NetBox with Gluware-discovered information according to the configured rules.
Run or schedule synchronization
Set exclusions and sync schedules for devices and sites. Incorporate NetBox operations into broader processes where required.
THE BUSINESS CONTRIBUTION
Connect the capability to visible value.
The team can connect fleet management and business-driven network changes to the source of truth it already uses. The integration supports a shared operating process while preserving the distinction between intended data and observed network state.
PART OF THE FULL STACK
Connect the work to the wider platform.
The native NetBox integration synchronizes configured device and site data. NetBox can own intended properties, and Gluware can supply discovered properties, according to the mappings. Device Manager discovers the fleet; CME (Config Model Editor) provisions modeled configuration; Network RPA coordinates wider processes.
Functional lifecycle components
Device Manager
Discover and inventory devices, inspect configuration and software state, and maintain the fleet information that network automation depends on.
Orchestration & integrations
Network RPA
Build and run visual processes that connect Gluware applications, external systems, operational logic, scheduling, and traceable tasks.
Functional lifecycle components
Config Model Editor
Model multi-vendor CLI and API intended configuration state with declarative enforcement.
Put NetBox Integration to work.
See how this capability can support your next network automation outcome.
CAPABILITIES THIS COMPONENT SUPPORTS
See the functional value.
Network discovery & onboarding
Discover the fleet, establish device context, and turn existing configurations into models your team can manage.
Cross-system orchestration
Connect network tasks, source-of-truth data, service-management steps, external executors, and records in a repeatable process.
Device inventory
Maintain discovered hardware, software, configuration, site, and advisory information in a shared device inventory.