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. Once you selected the integration, you can then specify basic settings like the integration name, escalation policy, names of the recipients/groups for which the alerts must be assigned to.

4. Once you click save, the API Integration will be created, and you will be given a unique URL which acts as the access point and needs to be configured at the source (in this case NinjaOne), to send alerts. You can find the integration you just created, and you can give advanced settings and define various configurations for the alerts to be received and processed. For example, you can define when to open and close alerts based on the payload obtained from the API call, filters etc.

5. Make a note of the API URL, which will be used in NinjaOne, so it calls a HTTP POST request to this URL with the body in JSON format containing the alert specic information.

6. Under 'Rules for Opening and Closing Alert' under Advanced Settings of Page: 3 of 8 the Inbound Integration, add the following values for each of the fields.

• • 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 can similarly define mappings as you want, owing to the $exibility provided by AlertOps’ OpenAPI/Plug-and-Play integrations. You can provide other filters and match with regex expressions as well. You can also test the generated URL with the sample data that you add.

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.

   

Thats it! You have congured an Webhook for a monitor. Any alert will be sent to AlertOps for incident management.

Message logs, alert-specific information can be viewed in the “Inbound Log” section in AlertOps Dashboard. Alerts can be viewed in the ‘Alerts’ tab as well.

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.