• Products
  • Get started
  • Documentation
  • Resources

Integrate Opsgenie with N-ABLE N‑central RMM

Solariwinds MSP Logo


What does the integration offer?

Use the N-ABLE N‑central RMM integration to send N‑central RMM issues to Opsgenie with detailed information. Opsgenie acts as a dispatcher for N-ABLE N‑central RMM alerts, determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, iOS & Android push notifications, and escalates alerts until they are acknowledged or closed.

How does the integration work?

  • When an issue is created in N-ABLE N‑central RMM, an alert is created in Opsgenie automatically through the integration.

  • When the issue's state turned back to Normal in N-ABLE N‑central RMM, the related alert is closed in Opsgenie automatically.

  • When the issue is acknowledged in N-ABLE N‑central RMM, the related alert is acknowledged in Opsgenie automatically.

Set up the integration

N-ABLE N‑central RMM is a bidirectional integration. Setting it up involves the following steps:

  • Add an N-ABLE N‑central RMM integration in Opsgenie

  • Configure the integration in N-ABLE N‑central RMM

Add an N-ABLE N‑central RMM integration

If you're using Opsgenie's Free or Essentials plan or if you’re using Opsgenie with Jira Service Management's Standard plan, you can add this integration from your team dashboard only. The Integrations page under Settings is not available in your plan.

  1. Go to Teams and select your team.

  2. Select Integrations on the left navigation and then select Add integration.

Adding the integration from your team dashboard will make your team the owner of the integration. This means Opsgenie will assign the alerts received through this integration to your team only. Follow the rest of the steps in this section to set up the integration.

To add an N‑central RMM integration in Opsgenie:

  1. Go to Settings > Integrations.

  2. Select Add integration.

  3. Run a search and select “N-ABLE N‑central RMM”.

  4. On the next screen, enter a name for the integration.

  5. Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.

  6. Select Continue.
    The integration is saved at this point.

  7. Expand the Steps to configure the integration section and copy the API URL.
    You will use this URL while configuring the integration in N-ABLE N‑central RMM later.

  8. Select Turn on integration.
    The rules you create for the integration will work only if you turn on the integration.

Configure the integration in N‑central RMM

  1. In N‑central RMM, select the user icon at the top to go to the Modify User page.

  2. Select User Details.

  3. Select Notification Method.

  4. Select ADD.

  5. Select Third Party Integration - HTTP for the notification method.

  6. Paste the URL you copied while adding the integration in Opsgenie into Target URL.

  7. Select Save.

Integrate via OEC

Use Opsgenie’s OEC and the N‑central RMM script to update alerts on N‑central RMM. With this setup, you can deploy your own script, modify the ones provided, or run customized actions on N-central RMM. To use the N‑central RMM integration package, complete the following steps:

  1. Download the latest version of OEC for the N‑central RMM package, go to the oec-scripts repository.

  2. Install the package.

For Windows

Unzip Opsgenie integration zip file which contains the OEC package into a directory (C:\opsgenie\oec is the preferred path). Learn about installing OEC on Windows.

To execute actions in N-ABLE N‑central RMM, OEC gets the configuration parameters from the configuration file (found under the directory where the zip file is extracted). If you used the preferred path in Windows, it is C:\opsgenie\oec\config.json.

Learn about running OEC.

Configure N-ABLE N‑central RMM integration for OEC

To execute actions in N-ABLE N‑central RMM, OEC gets the configuration parameters from the configuration file. Learn more about running OEC.





Copy the API key from the N‑central RMM integration you've created



Your N‑central RMM username



Your N‑central RMM password



The N‑central RMM URL


Sample parameters sent to OEC

(in JSON format)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 { "type":"nablencentral", "alertId":"0e321daf-6532-4277-a61c-83d90dea9969", "customerId":"d17aae0e-7730-4788-bbd5-a306816287d3", "action":"Acknowledge", "mappedActionV2": { "name":"acknowledgeNotification", "extraField":"" }, "integrationId":"2bdcf8c9-a423-4efd-957c-07ee7de236ea", "integrationName":"AppMon", "integrationType":"AppMon", "sendViaOEC":true, "activeNotificationTriggerId":"", "userName":"", "password":"", "url":"", "alias":"b324f7e2-c747-47bb-83d5-17b6a8eafaf8" }


Still need help?

The Atlassian Community is here for you.