Itential details FlowAgent demo syncing NetBox and devices

Itential demonstrated a FlowAgent that synchronizes NetBox and devices in both directions, updating inventory and device configuration without manual steps; this matters for IT leaders who need an accurate network source of truth and fewer reconciliation tasks.

Research overview

The vendor presented a live demo showing a FlowAgent that populates a NetBox instance from a network device and, in reverse, applies NetBox data to a device. The demo produced a full report with links to created records and completed the device-to-NetBox run in roughly 143 seconds.

Key findings

The agent created 54 interface records, captured IP addresses and descriptions, and used bulk-create operations to add objects to NetBox; the reverse agent read NetBox as source of truth and pushed missing configuration to the device with idempotent behavior. The run produced a hyperlink-rich report that referenced each created resource.

Technical breakdown

The implementation used four Model Context Protocol (MCP) tools for show commands, list and bulk create operations, and device configuration, together with a system prompt that set operational guardrails. FlowAI performed step sequencing so no custom code or separate orchestration logic was required to execute the flow.

Operational impact

Automated synchronization reduced manual inventory reconciliation, runbooks, and ticket work by replacing discrete human update steps with an agent-driven process. For operations teams, the agent removed routine synchronization tasks and left staffing available for other activities.

Demonstration timeline

The session covered site creation, Application Programming Interface (API) token refresh, MCP server connections, and running the sync flow; published timestamps in the demo include the sync start and results review at about 2:02 and 4:00, agent build steps at 5:59, and reverse sync completion around 10:24 to 12:22. The speaker also walked through the transcript of actions and verifies the pushed configuration on the device.

The overall takeaway is that an agent-based flow can maintain NetBox alignment with device state and can push NetBox-specified configuration back to devices; this “Blog Signals brief” is a fact-based summary of the vendor blog.