Integrating with SolarWinds N-central

Use this article as a guide to create and maintain an RMM integration with SolarWinds N-central, which gives you information about CPU, memory, last reboot, etc.

To integrate with SolarWinds' cloud-based RMM software, see Integrating with MAXfocus (aka Solarwinds MSP RMM) instead. MAXfocus is currently rebranding.

It should only take about an hour to get up and running with your RMM. This is a rough estimate based on our experience with several partners who integrated with their RMM.

The N-central sync described below will do the following:

  • Discovers all customers and devices in N-central
  • Matches customers to organizations in IT Glue using the ​N-central Customer Name field​
  • Suggests organizations based on name and pattern recognition
  • Matches devices to configurations in IT Glue using a MAC address or serial number
  • Suggests configurations based on exact name
  • (Optional) Site matching
    Used to match sites to sub-organizations in IT Glue

    For more information about the device mappings, see RMM Field Mappings.

Steps to integrate:

  1. Prerequisites
  2. Set up a secure connection & configure RMM
  3. Enter your RMM credentials
  4. Wait for the sync to complete
  5. Organization matching
  6. Configuration matching

1. Prerequisites

  • Manager or Administrator level access to IT Glue.
  • If you're integrating with a PSA and an RMM, you will want to first sync your RMM to your PSA and your PSA to IT Glue to make sure that the required data is available for matching.
  • A Manager role will only be able to see RMM matched/unmatched data for organizations that they have explicit access to. To grant access to RMM data for all organizations, refer to Step 7 of our Adding and removing users KB article.

2. Set up a secure connection & configure RMM

  • An SSL connection with a valid certificate (not self-signed) to your RMM is required.
  • You need to create a dedicated N-central integrator login, which is a user account created at the Service Organization (SO) level that has read-only access permissions to all clients.*
    • Note that the initial password is a temporary password. You must login to N-central and change the password to complete the registration process for the created account. Otherwise, IT Glue will be unable to access the API.
  • In addition to the SO user's credentials, you need the Fully Qualified Domain Name (FQDN) of the N-central server.
Note: If you are using N-central 11, follow the instructions in our Creating an integrator login in N-central 11 article to create the integrator login.

3. Enter your RMM credentials

  1. Open IT Glue.
  2. Navigate to Account > Integrations and click +New.
  3. Click the N-central option.

  4. Enter your N-central FQDN ( and login credentials. Click Connect.

    Note: To add a custom port for API traffic, you can add the port to the FQDN. For example, to add port 3000, your FQDN would look something like this:

  5. Choose between Customers and Sites, see the table below the screenshot for more information. Click Save.

    Option Description


    Matching on customers will allow you to map to top-level organizations in IT Glue.


    Matching on sites allows you to map to organizations and sub-organizations in IT Glue.

    Note:You can change this preference at any point. If you change your preference later, existing matches will be reset. For more information about sub-organizations, see Working with sub organizations.
  6. Start a manual sync by navigating to Account > Integrations, clicking Actions and Start Manual Sync. When the sync is complete, the status column changes from Syncing... to OK.

5. Organization matching

IT Glue discovers organizations and configurations and tries to match them to data in your account. The matching logic is at the top of this article. Anything that isn't automatically matched will need to be manually actioned.


  1. From Account > Integrations, find your RMM in the list and click on Actions and then Matching.
  2. Start with the Unmatched filter to review unmatched organizations.
  3. If you're happy with a suggested match, click Accept Suggestion to accept it:

    Or, you can search for and choose a different organization using the Match To column. You can also choose to ignore organizations, which means they won't count as unmatched items in subsequent syncs.
    Warning. If you don't see an organization, you can choose the Create Organization action to create (import) it. But make sure there is nothing to match first, so that you don't create a duplicate organization.
  4. Keep going through all your unmatched organizations until they are all matched.
  5. If you change your mind about any of the matches, click Actions, choose Change Match, and then manually search for and choose a different organization.

6. Configuration matching

Next, go through the same process to match configurations as you did for organizations.

  1. To begin, click the Matched filter, pick a matched organization, and then choose the Match Devices action.

  2. You should first review your matched devices to see if everything looks okay.

  3. Next, click the Unmatched filter and start matching any remaining configurations until all are actioned (matched, ignored, or created).
  4. Before you create configurations, first match any of the devices that we couldn't match based on MAC addresses or serial number, for example, virtual servers. When you're done matching, you can create (in bulk or individually) any of the remaining devices coming in from your RMM.
    Important. Assets created from RMM data will not sync with your PSA unless you manually edit and save the asset.
  5. Repeat for each organization until all configurations are actioned.

Once everything is matched, the RMM setup is complete. At any time, you can come back to these instructions to discover and match new organizations and configurations from your RMM.


Related articles

Was this article helpful?
1 out of 2 found this helpful
Have more questions? Contact us