Device Management

Domotz

Bring your Domotz Collectors and monitored devices into Dex so you can browse network inventory in plain language.

Dex connects to the Domotz Public API v1 so admins can browse network monitoring inventory conversationally - read a Collector (agent), list and inspect the devices it monitors, and check network topology, interfaces, and active IP conflicts. Read-only on this first ship: Dex reads the scoped surface but does not make mutating writes. Available as an MSP global app: one shared Full Access API Key covers every Collector on the account, and each Dex tenant is confined to its own Domotz Collector via agent_id, so each customer sees only its own network.

Start free →

What Dex does with Domotz

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Read a Domotz Collector (agent) mapped to this tenant
List and inspect the devices a Collector monitors, including hidden and excluded devices
Review network topology captured by the Collector
List monitored network interfaces on the Collector
List active IP conflicts detected on the network
Deploy as an MSP global app - one shared Full Access API Key, each customer confined to its own Collector via agent_id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Show me the Domotz Collector mapped to this tenant
>List the devices this Collector is monitoring
>Are there any active IP conflicts on the network?
>What does Domotz have on file for the device named "FIN-SWITCH-01"?
>Show me the network topology for this Collector

Policy actions

Every action Dex can take on Domotz is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`domotz_list_agents`	List every Domotz Collector (MSP master connection only)	—
`domotz_get_agent`	Read one Domotz Collector by id (path-forced on a scoped child)	—
`domotz_list_devices`	List devices on this Domotz Collector	—
`domotz_get_device`	Read one device under this Domotz Collector	—
`domotz_get_network_topology`	Read network topology for this Domotz Collector	—
`domotz_list_network_interfaces`	List monitored network interfaces for this Collector	—
`domotz_list_ip_conflicts`	List active IP conflicts for this Domotz Collector	—

How to configure Domotz

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In the Domotz Portal, go to Settings > API Key and create a Full Access API Key.
2
Copy the API Key and the Endpoint host shown once at creation (e.g. api-us-east-1-cell-1.domotz.com).
3
In Dex, enable the Domotz integration on the MSP-master connection and paste the API Key and cell hostname; leave agent_id blank on the master.
4
Dex validates the credentials with a live read before saving, then uses GET /public-api/v1/agent on the master to look up each tenant's Collector id.
5
For MSPs, map each Dex tenant to its Domotz Collector id in Global Apps > Domotz - do not write the API Key or agent_id onto a child connection.

Credentials required

api_key: Domotz Full Access API Key (secret; written on the MSP-master connection only)
api_host: Domotz Public API cell hostname, e.g. api-us-east-1-cell-1.domotz.com (hostname only)
agent_id: Domotz Collector (agent) id - leave blank on the MSP master; set per tenant via Global Apps > Domotz mapping

Requirements

•A Domotz account with a Full Access API Key (not an Agent Activation only key)
•Read-only on this first ship - Dex browses Collectors, devices, and network detail but does not make mutating writes
•Dex Go is off for Domotz - there is no end-user self-service, since the API cannot cryptographically bind a Dex user to a Domotz identity
•For MSPs, deploy as a global app with one shared key and per-tenant Collector scoping via agent_id