Skip to main content
The Domotz integration brings collector, network, device, monitoring, and alert data into MSPortal. After connecting and mapping your account, you can review site health under Devices > Networks, link sites to MSPortal locations, and add Domotz network health to client reports.
Domotz is currently a Pilot integration available to selected tenants. If you do not see the Domotz card in Settings > Integrations, contact support@msportal.ai.

​
What Gets Synchronized

Organizations and Collectors

Domotz organizations, API-enabled collectors, their status, and company mappings

Networks and VLANs

Site networks, VLAN counts, ISP details, WAN addresses, uptime, and internet-speed results

Managed and Discovered Devices

Managed inventory, online state, and devices Domotz has discovered on the network

Monitoring and Alerts

TCP and SNMP sensor state, IP conflicts, packet loss, and active alerts
These setup steps are for MSP staff. Viewing the Networks tab uses your Devices permissions and company scope.

​
Prerequisites

  • A Domotz account with Public API access
  • A Domotz API key with Full Access
  • At least one Collector with API access enabled
  • MSPortal integration management permission for credential testing, saving and deletion
  • MSPortal companies to receive your Domotz organization and collector mappings
Create MSPortal locations before setup if you want to link Domotz sites during the wizard. Site linking is optional and can also be completed later from Devices > Networks.

​
Part 1: Create a Domotz API Key

1

Open the Domotz Portal

Sign in to the Domotz Portal and open its API access settings (Settings > API Key).
2

Create a Full Access API key

Create an API key with Full Access, then copy both the key and its assigned API server URL.
Each API key is tied to a regional server, for example https://api-us-east-1-cell-1.domotz.com/public-api/v1. Use the exact URL shown with your key.
3

Confirm Collector API access

Make sure at least one Collector in the Domotz account has API access enabled. Collectors without API access cannot be synchronized.

​
Part 2: Connect and Map Domotz

1

Open the Domotz setup wizard

Go to Settings > Integrations, find Domotz, and open its setup page.
2

Test the connection

On Connect, enter the API server URL and API key, then click Test connection.
Domotz API server URL and blank API key field.

The Connect step before credentials are entered.

A successful test shows how many collectors the API returned. Review any warnings about disabled Collector API access, unavailable optional capabilities, or API quota usage.
3

Create the integration

Click Create integration, then click Next. MSPortal stores the API key in its secure credential vault and starts the initial discovery.
4

Map companies

On Map, link each Domotz organization to the matching MSPortal company. A Collector that does not belong to a Domotz organization appears as an Orphan Collector and can be mapped independently.Use Quick Match or the company picker to stage links, then select Import Selected to save them. Leaving the step also saves pending links, and moving forward after edits queues a synchronization. Creating a new company saves the company immediately, but its link stays pending until you save. Removing an existing mapping saves immediately. If a batch save fails part way, some links are saved, so check the list before you retry.
5

Map sites

On Map sites, link each mapped Collector to an existing MSPortal location. Use the location picker in the Site column.A Collector must be mapped to a company before it can be linked to one of that company’s locations. Selecting or removing a location saves immediately. This step is optional.
6

Review data coverage

On Review, check company and Collector mapping, Collector availability, managed and discovered devices, networks and VLANs, inventory field coverage, monitoring variables, active alerts, and API usage.Counts update while the initial synchronization runs. Click Complete setup when you are finished; synchronization can continue in the background.

​
Review Network Health

Open Devices, then select the Networks tab. The tab appears when your tenant has a Domotz connection and follows the company scope selected in MSPortal’s top bar. The table shows one row per mapped Collector:

​
Find and Investigate a Site

1

Set the company scope

Use the company selector in the top bar to show all permitted companies or narrow the page to one company.
2

Filter or sort the table

Search by site or ISP, filter by company, location, or issue state, and sort the supported columns. Use the column selector to show only the fields you need.
3

Review issues

A site with none of the counted issues shows Healthy. Healthy covers only the counted issues, so also check Last synced and any warnings from setup. When a site has issues, point to or focus the issue badge to see the breakdown of IP conflicts, failing TCP sensors, active alerts, and packet-loss findings.
4

Open the site's devices

Click the value under Devices online to open Devices filtered to the linked location and company. If the site is not linked to a location, MSPortal filters by company only.
Users who can manage Devices can update site links directly from the Networks table.
1

Start editing the location

In the site’s Location cell, click Edit.
2

Choose the location

Search the locations belonging to the mapped company and select the correct one. The table updates after the link is saved.
To remove an existing link, click Edit and select Remove link. You can also manage the same links by reopening the Domotz setup wizard and selecting Map sites.

​
Add Domotz Network Health to a Report

In the Report Builder, add the Domotz Network Health block from the integration blocks. The block summarizes Collector availability, managed-device state, networks and VLANs, monitoring issues, and internet-speed results for the report’s company scope. When editing the block, you can choose whether to include discovered-device counts, active Domotz alerts, and internet-speed results.
The reporting block requires a Domotz connection and permission to read Devices.

​
Manage the Connection

1

Reopen Domotz

Go to Settings > Integrations and open Domotz.
2

Update credentials

Enter the new API server URL and key, select Retest connection, then select Save connection.
3

Change mappings or site links

Reopen the Map step for companies, or Map sites for locations. You can also edit the Location column under Devices > Networks.
4

Disconnect

Use the delete action in the wizard and confirm. This removes the integration and its stored credentials.
Users with integration read access can review the connection. Testing, saving and deleting credentials needs integration management permission.

​
Troubleshooting

​
Frequently asked questions

Domotz is a pilot integration available to selected tenants. Contact support@msportal.ai to ask for access.
No. Use a Full Access Public API key and its assigned API server URL, with at least one API-enabled Collector.
No. Select Create integration or Save connection after testing.
A Collector that does not belong to a Domotz organization. Map it on its own to the MSPortal company it serves.
No. Selecting or removing a location saves immediately.
No. It means no IP conflicts, failing TCP sensors, active alerts or packet loss were counted. Check Last synced and setup warnings too.
No. Synchronization continues in the background. Check the Review counts and the Networks tab.

Devices

Review and manage synchronized devices

Reporting

Build client-facing reports with integration data

Companies and Locations

Create and manage company locations

Integrations Overview

Explore all available integrations