Integration — HaloITSM

What you get

Halo, populated from discovery.

Insights keeps HaloITSM's asset register current straight from discovery.

Halo stays populated

Insights pushes each discovered asset into Halo as a configuration item via the Halo REST API, the register stays current from discovery.

No duplicates

An idempotent upsert keys on the uControl asset UUID and remembers Halo ids, so re-runs update instead of duplicating; unchanged assets are skipped.

Sub-CIs & relationships

Disks, peripherals and host-to-component relationships flow through, not just flat hosts.

Scoped push

Control what syncs by category, lifecycle state, owner or site.

Asset types handled

Maps asset types to Halo asset types and auto-creates any that are missing.

Owners resolved

Owners are resolved by email and attached to the Halo CI.

Available today · Insights

Discovery keeps HaloITSM current.

Insights authenticates with OAuth2 client-credentials and upserts each discovered asset into Halo, keyed on the asset UUID with a payload hash, so the sync is safe to re-run and never duplicates.

OAuth2 client-credentials against the Halo REST API
Idempotent, UUID-keyed upsert with change detection
Maps asset types, custom fields, owners and relationships
Manual sync today, scheduled auto-sync planned

On the roadmap · Core

Data quality, uMap modelling and publish-back.

Planned for Core: import Halo assets for data-quality reporting, use them in uMap for application and service modelling, and publish the modelled services back to Halo, the same two-way pattern as EasyVista.

Import Halo assets for data quality and reporting
Model applications and services in uMap
Publish modelled services back to Halo
On the roadmap, not yet available

HaloITSM + uControl