Skip to content
  • There are no suggestions because the search field is empty.

NinjaOne

AlertOps and NinjaOne

AlertOps’ alert-management system can be integrated with NinjaOne to receive and respond to all predefined status-mapped alerts through email, SMS, push notifications, or phone alerts.

AlertOps ensures that job/alert statuses reach the appropriate team by using workflows, escalation policies, and schedules. Based on your ruleset, incidents can be opened and closed automatically depending on the type of alert NinjaOne reports.

This flexibility is possible because AlertOps supports an adaptable API/Webhook configuration that works seamlessly with NinjaOne's alert and notification capabilities.

AlertOps – Inbound Integration

You can define rulesets in AlertOps so NinjaOne can push alerts to the AlertOps platform. AlertOps will ensure the notifications are routed to the correct person/team using escalation policies, schedules, and workflow features.

AlertOps provides inbound integrations for numerous monitoring, chat, and ITSM tools. You can configure one specifically for NinjaOne.

At a high level:

  1. You create an API Integration in AlertOps by defining settings such as Integration Name, Escalation Rules, and Recipient Users/Groups.

  2. AlertOps generates a unique API URL for that integration.

  3. That URL is used by NinjaOne as a webhook endpoint to send alerts.

  4. Alerts arriving through this URL create or close incidents based on the payload and rules you’ve configured.

Configure Inbound Integration in AlertOps

  1. In Configuration → Integrations, from the Inbound Integrations section, select API and click Add API.

  2. Choose NinjaOne from the list of available integrations
    (or choose Custom and add the field mappings manually as described later).

  3. Enter basic settings such as:

    • Integration Name

    • Escalation Policy

    • Recipient Users/Groups

  4. Save the integration. AlertOps will generate a unique API URL that NinjaOne will use to send POST requests.
    You can further configure advanced settings such as URL mappings, filters, escalation rules, and open/close criteria.

  1. Copy the API URL. NinjaOne will POST JSON data to this endpoint.

  2. Under Advanced Settings → Rules for Opening and Closing Alert, enter the following mappings:

    • SourceId: deviceId

    • Source / Source Name: NinjaOne

    • Source Status: status

    • Subject: <message>

    • Open Alert When Value: Triggered

    • Close Alert When Value: Reset

    • Long Text: <message>

    • Short Text: <data^message^params^nodeDisplayName> - <data^message^params^conditionName>

Sample Data to Paste

 
{
"id": 327451,
"activityTime": 1762192612.839617,
"deviceId": 62,
"seriesUid": "d0d19953",
"activityType": "CONDITION",
"statusCode": "TRIGGERED",
"status": "Triggered",
"sourceConfigUid": "b3017678",
"sourceName": "agent offline condition",
"message": "Device 'ABC-RAS01' is offline for 15 minutes triggering condition 'Server Offline'",
"type": "Condition",
"data": {
"message": {
"code": "conditions_device_offline_triggered_with_cond_name",
"params": {
"nodeDisplayName": "ABC-RAS01",
"conditionName": "Server Offline",
"nodeContactTime": "2025-11-03T17:41:30.552Z",
"durationOffline": "15"
}
}
}

Select the green check mark to save.

You may configure additional mappings, regex-based filters, and use the generated URL for testing with sample data.

Configure Integration in NinjaOne

(Webhook triggers work only in the new UI)

  1. Webhooks in NinjaOne send data to a specified URL when certain events occur.

  2. Go to Administration → Apps → Notification Channels.

  3. Click Add, then select Webhook.

  4. Enter a name and paste the AlertOps API URL.

  5. Enable the webhook.

  6. Click Save to establish the connection.

  7. Attach this webhook to a Device Policy under the Channels dropdown.

Once configured, any alert generated by NinjaOne will be sent to AlertOps for incident management.

Inbound logs and alert details can be viewed in the Inbound Log section in AlertOps. Alerts can be viewed in the Alerts tab.

Alert Triggering Information

  • AlertOps automatically creates a new incident when NinjaOne sends an alert where status = Triggered.

  • If an incoming “Triggered” alert matches an already open alert, AlertOps detects it as a duplicate and ignores it.
    The alert will still appear in Inbound Messages as Mapped Appended.

  • AlertOps automatically closes the same incident when an alert with device status Reset is received.