Skip to content
Integrations & automation

A CMDB
that feeds
itself

A CMDB is only useful if its data stays current. iTop provides a REST API and collectors to feed the repository from existing sources.

Two complementary approaches

REST API or collectors: choose according to the need

Both modes can be used separately or combined.

The REST API lets external systems read, create, update or delete iTop objects through standard HTTP calls.

Collectors automate recurring synchronization with mapping, reconciliation and logs.

🔌
REST API

CI creation, updates, BI exports and monitoring-triggered tickets.

⚙️
Collectors

Scheduled sync with AD, inventory, virtualization, IPAM or cloud.

🔁
Reconciliation

Rules compare source data and iTop without uncontrolled overwrites.

📋
Logs

Reports show created, updated, ignored or obsolete objects.

Supported sources

Connectors for existing systems

🌐

teemIP / IPAM

IP blocks, subnets, addresses and network equipment.

👥

Active Directory / LDAP

Users, groups, computers and contacts.

☁️

Virtualization & cloud

VMs, clusters, cloud resources and accounts.

📡

Monitoring

Ticket creation from Nagios, Zabbix, PRTG or similar tools.

🗄️

Inventory

OCS Inventory, GLPI, Lansweeper or existing exports.

🔒

Security

Enrichment with vulnerabilities and risk levels.

Synchronization pipeline

Reliable collection in 5 steps

1

Extract

The collector queries the source and retrieves raw data.

2

Transform

Values are normalized according to the target mapping.

3

Reconcile

iTop compares incoming data with existing records.

4

Synchronize

Creation, update or obsolescence according to rules.

5

Log

A report highlights errors and changes.

Your CMDB deserves live data

We analyze your sources and build the collection architecture adapted to your IT estate.