N-able N-central RMM

Hudu offers a native integratoin with N-Central RMM, allowing you to seamlessly connect and sync data between the two platforms.

Before getting started, we recommend reviewing our Understanding Integrations article to learn basic concepts and useful tips.

What You’ll Need

Before you begin, make sure you have:

• Access to retrieve JWT Token from N-Central RMM
• N-Central version 2024.3
• Admin or Super-Admin user role within Hudu

Integration Features

Hudu's integration with N-Central RMM allows you to sync over:

• Customers
  • Create client spaces within Hudu directly from N-Central customers, or seamlessly merge them into existing (already created) client spaces
• Sites
  • Pull in Sites from customers in N-Central
• Devices
  • Pull device information from N-Central, sorted into asset layouts based on set sort rules

What Hudu needs from N-Central RMM

• N-Central Domain
• JWT Token

Enabling the Integration

Integrations can be enabled at any point during your Hudu environment testing and/or during production. Integrations can be merged into your existing documentation based on set rules; providing the ability to start with integration setup, or easily connect them at a later date. 

To enable the N-Central RMM integration:

• Navigate to Hudu admin area >> Integrations
• Select N-Able N-Central RMM from the list

Obtaining the N-Central RMM Information

• Navigate to profile in the top right
• Select API Access
• Generate JSON Web Token

Setting up the Integration in Hudu

Step 1. Connect to N-Central

• Enter your N-Central RMM Fully Qualified Domain Name (without the https)
• Enter your JWT Token
• Select asset types to skip (optional)
• Select any additional options:
  • Auto-update names of Assets. If name is changed in N-Central RMM, the name will automatically be updated in Hudu
  • Do not update basic company details. This will prevent the company details from being changed in Hudu if they are changed in N-Central RMM
  • Sync detailed device information. This will bring over more device details such as, OS Features, Memory Information, OS Details, Media Access Devices, Folders, Motherboard Details, Network Adapters, Physical Drives, Processor Information, Patches, Applications, Ports, Services, Computer System Details, and Logical Devices
• Save the Settings

Step 2. Test Connection and run an initial sync

• On the integration overview page, click Test Connection
• If successful, start an initial sync to bring in N-Central Customers

Step 3. Match N-Central Companies

• Before companies from N-Central RMM can be brought into Hudu, they must be matched to:

  • Existing companies in Hudu, or

  • New companies you create in Hudu

• Hudu recommends matching one company first for testing to ensure data imports correctly

• When the integration runs successfully for the first time:

  • Customers from N-Central RMM are imported

  • They appear in the Matched Companies List for the integration

• Navigate to Hudu Admin → Integrations → N-Able N-Central RMM

• Open the integration and click Match Companies

• Review the list of companies and choose one of the following options:

  • Bulk create and/or match all companies

  • Match a company to an existing Hudu company

  • Create a new matched company in Hudu from an N-Central customer

  • Leave a company unmatched (it and its data will not be imported)

• After matching companies, re-run the integration import to populate data for the matched or newly created companies

Step 4. Run a Second Sync

• Once companies are matched, start a second sync to bring over N-Central Device Types
  • This is required to bring in the ability to skip certain device types

Step 5. Select N-Central Device Types to Skip

• After the second sync, navigate back to the Edit Settings page to choose Device Types to skip (optional)

Step 6. Choose where N-Central data will fill to

• Now that you've selected devices you would like to skip, you will need to tell Hudu where to put your N-Central data
• Select default asset layouts for your N-Central configurations and locations
  • You must select default asset layouts in order for N-Central data to be brought in
  • The default asset layouts hold any incoming information that doesn’t have a designated place
  • You must also first create the asset layouts in Admin > Asset Layouts
    •  If you don't see or have not created any asset layouts yet, you'll need to create these. Visit Asset Layouts for additional information!
• After you have selected the default asset layouts, run another sync to bring in the ability to further sort devices into additional asset layouts with Sort Rules
• Sort rules allow you to select which data types (from N-Central RMM) will be mapped into which asset layouts (within Hudu). They allow you to specify certain "rules" for asset types as to where they get placed; any asset types that are brought in, but are not told where to be placed via sort rules, will be placed into the corresponding primary sync location
• The asset layouts that you're choosing to sort into can be created beforehand (Hudu admin area >> Asset Layouts; ensure that they're marked active) OR you can create new asset layouts here

Step 7. Run a final sync

• After saving all the settings, start a final sync to bring in N-Central devices and locations

FAQ