Integrations
Domotz
Overview
This document provides a complete, beginner-friendly guide to integrating Domotz with Callgoose SQIBS using webhook notifications.
Domotz is a network monitoring and management tool used for device discovery, uptime monitoring, alerts, SNMP data, and remote access.
Domotz allows sending event-based webhook notifications when devices change state or when configured alerts are triggered.
Callgoose SQIBS automatically creates, updates, and resolves incidents based on webhook payloads.
This integration enables:
- Real-time incident creation in Callgoose SQIBS
- Automatic incident resolution when Domotz reports recovery
- End-to-end visibility from network device alerts → SQIBS incidents
- Customisable alert rules based on device offline/online, performance metrics, or SNMP values
If Domotz documentation does not publicly define some payloads or behaviour, it is mentioned professionally in the respective sections.
Prerequisites
Before proceeding, ensure you have the following:
- A Domotz account with permission to configure Alerts and Webhooks
- Domotz Agent (Collector) installed and connected
- A Callgoose SQIBS Webhook URL with API Token
Some Domotz webhook details are not publicly exposed; wherever information is unavailable, it is clearly mentioned.
1. Install Domotz
Domotz installation varies by platform. Below is the general workflow based on Domotz’s officially described onboarding steps.
1.1 Install the Domotz Agent
Install the Domotz Agent on your supported platform (Windows, Linux, NAS, or network appliance).
After installation, open the Domotz Agent setup page and authenticate using your Domotz account.
1.2 Activate the Agent
Provide the required details, name the Agent, and complete activation.
Once activated, the Agent begins scanning the network automatically.
1.3 Verify Installation
Ensure that:
- The Agent shows as “Online”
- Devices appear in the device inventory
- Alerts and monitoring sections are enabled
Domotz installation steps beyond this are platform-specific. No additional public details were available.
2. Obtain the Callgoose SQIBS Webhook URL
- Log into Callgoose SQIBS
- Navigate to the Webhooks/API integrations section
- Create a new webhook endpoint
- Copy the URL, for example:
https://****.callgoose.com/v1/process?from=domotz&token=xxxxx
Keep the token private.
This URL will be used inside Domotz.
3. Configure Domotz to Send Alerts to Callgoose
Domotz supports webhooks for alert notifications, but Domotz does not publicly document the exact JSON payload structure.
The steps below reflect the confirmed configuration flow, but payload examples are represented generically.
3.1 Enable Alerts in Domotz
In the Domotz dashboard:
- Open the device or network area
- Configure “Alerts” such as:
- Device offline
- Device online
- SNMP threshold
- Custom performance metrics
3.2 Create a Webhook Notification
Under the Domotz Alerts section:
- Choose Webhook as a notification method
- Add a new Webhook
- Paste the Callgoose API Endpoint
- Select POST as the method
- Select application/json as the content type
3.3 Define Webhook Payload
Domotz allows specifying a JSON body for the webhook event.
However, Domotz does not publicly provide the default variable names used in payload templates.
A general fallback payload (safe to use if official values are not available):
{
"device_id": "{{$device_id}}",
"device_name": "{{$device_name}}",
"alert_type": "{{$alert_type}}",
"status": "{{$status}}",
"timestamp": "{{$timestamp}}",
"message": "{{$message}}"
}
If Domotz supports different variables in your environment, they must be updated accordingly.
3.4 Save and Test
Use the built-in Test Webhook button (if available) to ensure Callgoose receives the request.
4. Example Payloads Sent to Callgoose SQIBS
Domotz does not publicly publish official webhook payloads.
Below are professionally constructed generic examples based on typical Domotz alert patterns.
4.1 Trigger (Device Problem)
{
"device_id": "device-123",
"device_name": "Office-Router",
"alert_type": "device_offline",
"status": "firing",
"timestamp": "2025-11-17T10:00:00Z",
"message": "Device is unreachable."
}
4.2 Resolve (Device Recovery)
{
"device_id": "device-123",
"device_name": "Office-Router",
"alert_type": "device_online",
"status": "resolved",
"timestamp": "2025-11-17T10:05:00Z",
"message": "Device is back online."
}
If your Domotz environment provides different field names, you must update API Filters accordingly.
5. Configure API Filters in Callgoose SQIBS
Set up two filters: one for firing, one for resolving.
5.1 Trigger Filter (Create Incident)
- Payload JSON Key: "status"
- Key Value Contains: firing
- Map Incident With: "device_id"
- Incident Title From: "device_name"
- Incident Description From: "message" (or leave empty to use entire payload)
5.2 Resolve Filter (Resolve Incident)
- Payload JSON Key: "status"
- Key Value Contains: resolved
- Incident Mapped With: "device_id"
This ensures the correct incident resolves when Domotz sends a recovery notification.
Refer to the API Filter Instructions and FAQ for more details.
6. Testing the Integration
Step 1 — Trigger a Test Event
Disconnect a monitored device to generate an offline alert.
Step 2 — Check Callgoose Webhook Logs
Verify that:
- Payload was received
- The status = firing
- The device_id value is correct
Step 3 — Trigger Resolve Event
Reconnect the device to trigger a resolved alert.
Callgoose should automatically close the incident.
7. Troubleshooting
No incident created
- Webhook not triggered inside Domotz
- Incorrect JSON key names
- Incorrect filter value (e.g., expecting firing but webhook sends something else)
Incident not resolving
- Resolve filter expects status = resolved
- device_id in resolve does not match trigger
Webhook failures
- Network restrictions blocking outbound requests
- Token or endpoint incorrect
- Domotz agent offline
Payload fields missing
- Domotz may use different variable names
- Capture an actual webhook in Callgoose logs and update filters
8. Conclusion
You now have a fully operational integration between Domotz and Callgoose SQIBS using webhook notifications.
Domotz detects network events or device health changes, sends payloads, and Callgoose automatically creates and resolves incidents.
This creates a complete monitoring → alerting → incident management workflow.
For further customization or advanced use cases, refer to the official documentation for both Domotz and Callgoose SQIBS:
