TransIT AI

Sync your inventory from NetBox

Pull your device inventory out of NetBox and keep it current — as a reviewed diff, never a blind mirror. Works in Transit 6.2.0 and later.

Once: add the NetBox controller

  1. Open the APIs rail → New API controller.
  2. Vendor: NetBox. Base URL: your instance plus /api — for example https://netbox.example.com/api.
  3. Paste an API token (NetBox → your profile → API Tokens). The preset sends it as Authorization: Token <key>; if yours is a v2 token (nbt_…), switch Auth to Bearer token instead. A read-only token is enough for everything on this page.
  4. Save. The NetBox request collection appears under the controller, and the AI can now answer questions from it through read-only, per-call approved lookups.

Each time: fetch and review the diff

  1. Click the import icon at the top of the sidebar (the same bulk-import used for SecureCRT, MobaXterm, ssh_config, and CSV) and choose NetBox under Or sync from a live source.
  2. Pick your NetBox session and Fetch active devices (or Fetch all statuses to include planned/offline gear).
  3. Review the three tabs:
    • New — devices Transit doesn’t have yet. Pick the auth profile they’ll use (NetBox doesn’t store device passwords, so credentials are always yours, mapped here), then adjust any row: name, host, vendor, group. Sites become sidebar groups; platforms become vendors; tags carry over. Name collisions arrive pre-suffixed and excluded, so nothing silently overwrites.
    • Changed — matched devices whose host, vendor, or site moved in NetBox. Every field is a separate accept/skip; your local settings (colors, terminal preferences, extra tags) are never touched.
    • Stale — devices whose NetBox entry is gone. Keep is the default; Unlink drops the NetBox association; Delete removes the device from Transit — and any deletes are re-confirmed by name before anything runs.
  4. Press Apply. The whole batch commits atomically: if one row fails, nothing is written.

Re-syncing

Run it again whenever you like — imported devices carry their NetBox identity, so the next fetch diffs instead of duplicating: unchanged devices don’t even appear, drift shows up under Changed, and removals show up under Stale. There is no background sync and no schedule; nothing happens unless you fetch, and nothing is ever written back to NetBox.