J
JOATOSIT Operations Platform
Browse documentation

Webhook notifications

Alerts & Notifications

The generic Webhook channel POSTs a structured JSON payload to any HTTPS endpoint you choose — ideal for custom integrations and automation tools (n8n, Zapier, Make, or your own receiver).

Creating a webhook profile

  1. In Settings, under Alerts, open Notification Profiles and create one.
  2. Name it.
  3. Set Channel to Webhook (generic JSON).
  4. Paste your endpoint URL into the Webhook URL field (e.g. https://example.com/hooks/alerts).
  5. Save, then attach the profile to an alert profile.

Like Slack and Teams, the URL is stored encrypted and never shown again, and there are no user recipients — the endpoint is the destination.

The payload

On each alert or clear, JOATOS sends a POST with Content-Type: application/json and a fixed structure:

{
  "event": "ALERT",
  "title": "Device Down",
  "message": "Server 1 is offline",
  "condition": "DOWN",
  "conditionDetail": null,
  "target": { "type": "SERVER", "id": "…", "name": "Server 1" },
  "site": "Head Office",
  "alertProfile": "Production servers",
  "tier": 1,
  "timestamp": "2026-07-04T09:15:00Z"
}
  • eventALERT or CLEAR.
  • title / message — the human-readable summary.
  • condition / conditionDetail — what tripped, with any detail.
  • target — the device, server, or monitor (type, id, name).
  • site, alertProfile, tier (escalation tier, or null), timestamp (ISO-8601 UTC).

The schema is fixed in this release — there are no custom templates or headers yet.

Helpdesk ticket channel

A related channel, Helpdesk ticket, turns an alert into a support ticket instead of a message. On the notification profile you set the ticket defaults — department, category, priority (or auto from alert severity), and assignee — plus an auto-resolve when the alert clears option.

  • If the same alert re-fires while a ticket is still open, JOATOS adds a comment rather than opening a duplicate.
  • This channel is only available when the Helpdesk module is enabled.

Notes & tips

  • A non-2xx response or network error is recorded as a failed send in the alert history.
  • Use the event field to distinguish an alert firing from it clearing in your automation.

Related