N-Able N-Central RMM Integration

If you are currently using IP restrictions in your firewall or within the product, allow these IP addresses:

  • 35.192.223.4
  • 35.224.156.102

Prerequisites

  • Create a Role for SaaS Alerts
  • Create an API Only User for SaaS Alerts and get API Key
  • Schedule an Automation Policy to store devices’ public IP addresses to the IPV4_PUB custom property

Creating a role for SaaS Alerts

  1. From within N-Central, navigate to Administration\User Management\Roles.
  2. Click Create Role.
  1. Name the Role. Suggestion: SaaS Alerts
  1. Scroll down Custom Properties\ View/Set and select Read Only. Then, go to Administration\User Management and select Read Only for Access Groups, Roles and Users.
  1. Scroll down to Devices and select Read Only from the Action menu to add Read Only to all sub items.
  1. Scroll to the bottom and click Save.

Creating an API Only user

  1. Navigate to Administration\User Management\Users.
  2. Click Create User.
  3. Enter the user information and password.
  4. Click the Role tab and click Assign Roles.
  5. Select the role you created earlier and click Assign.
  1. Click the Access Groups tab and click Assign Access Groups.
  2. Select All and click Assign.
  1. Click the User Details tab, and then the User Information sub-tab
  2. Ensure that MFA Not Required is selected.
  1. Click the API Access tab, and ensure that API-Only User is selected.
  2. Click Save.
  3. Click OK and then Save/Cancel.

Scheduling an automation policy for public IP addresses

  1. Navigate to Administration\Custom Properties.
  2. Click Add, then select By Devices\Text Type.
  3. Set the Property Name to IPV4_PUB, the Default Text to Public IPv4 Address, and ensure that all Operating Systems and all Device Classes are selected by pushing the >> arrows on each list.(NOTE: As new Operating Systems are added to N-Central, you will need to edit this property and ensure that the new OSes are moved to the Selected Operating Systems on the right.)

  4. Navigate to Configuration\Scheduled Tasks\Script/Software Repository.
  5. In the Search bar at the top, enter public, and then click Clone on Get Public IP Address.
  6. Utilize the following information in the Clone Repository Item screen.
    - Name: Get Public IP Address and Save to IPV4_PUB.
    - Description: Leverage whatsmyip.com to retrieve public IP of device and store in the IPV4_PUB Custom Property.
  7. Navigate to Actions\Run an Automation Policy.
  8. Utilize the following information in the Automation Policy Task\Details tab.
    • Task Name: Get Public IPv4 Address and store in IPV4_PUB.
    • Repository Name: Get Public IP Address and Save to IPV4_PUB.
    • Output Parameter (IP): IPV4_PUB

  9. On the Automation Policy Task\Targets tab, ensure Windows Agents is in the Selected Filters section.
  10. On the Automation Policy Task\Schedule tab, ensure that it is set to Recurring and to repeat every 5 minutes.(Note: You can select 10 or 15 minutes, but Unify functionality will be more accurate with every 5 minutes.)
  11. Click Save.
  12. To verify that the process worked, follow the steps below.
    • Wait 5 minutes (or 10, 15 depending on your schedule selection above).
    • Go to a Windows device, and navigate to Settings\Custom Properties.
    • Ensure that the IPV4_PUB custom property has been populated with the correct Public IP address for that device.

Connecting SaaS Alerts to N-Central

  1. Find your MSP’s organization in SaaS Alerts, or create a new organization for your MSP. You can do that on the SaaS Alerts Organization page.
  2. Click N-Central in the list of products.

    3. NOTE  You may receive an alert indicating that an existing N-Central integration already exists. Unless you have multiple instances of N-Central, you should cancel, or you will have duplicates.

  3. Populate the connection wizard with the Nable N-Central API info you collected earlier.
  4. Click Next.
  5. You are now ready to configure Unify organization mapping. Refer to Unify overview.