Skip to main content
Triggr works with Domotz collectors, devices, monitoring data, alerts, power actions and Access Management users. You need the Domotz account owner, or a user whose role includes the API Keys permission, such as Administrator (see Domotz’s Role Based Access Control guide).

​
Set up Domotz

1

Create a Full Access key

In the Domotz Portal, go to Settings > API Keys and click Create an API Key, not Create a Collector Activation Key. Enter your password, click Unlock, name the key and click Create.
2

Copy the key and endpoint

Click Copy next to API Key and note the host in the Endpoint URL, then click Done. Domotz shows the key and endpoint only in this dialog.
See Domotz’s Domotz API guide.

​
Connect it in Triggr

1

Open the integration

Go to Integrations > Domotz and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the host and key

Enter the API Endpoint Host and API Key, then click Save Configuration. For the endpoint https://api-eu-west-1-cell-1.domotz.com/public-api/v1/, the host is api-eu-west-1-cell-1.domotz.com.
The Domotz configuration window with API Endpoint Host and API Key fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
In workflows, run List collectors to find collector IDs (agentId) and Collector devices list to find device IDs (deviceId). Time ranges use UTC in the format yyyy-mm-ddThh:mm:ss.

​
Troubleshooting

API Endpoint Host takes the host name only, with no https://, path or spaces.
Check the key is a Full Access key, pasted in full, still listed on API Keys, and that the host matches its Endpoint. If you’ve lost either value, create a new key and click Edit on the Base Configuration card.
The key sees only the collectors its creator can access. Create it as the account owner or an Administrator.
Your account has hit a Domotz API limit. Run API usage and limits to check, and spread large workflows out.