Setting up the NinjaRMM integration

   This article has been moved!

We've recently updated our support center articles - Please bear with us while we make the transition. This article can now be found here!

Before starting to connect an integration, please read:

Integration Features

Hudu's integration with NinjaOne RMM allows you to sync over:
  • Organizations.
    • Create client spaces within Hudu directly from Ninja companies, or seamlessly merge them into existing (already-created) client spaces.
  • Devices.
    • Pull device information from NinjaOne; sorted into asset layouts based on set sort rules and your primary sync location(s).

What Hudu needs from NinjaOne

  • Client ID.
  • Client Secret.

 

Guides

Enabling Integrations

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 NinjaOne integration:
 
  • Navigate to your Hudu admin area >> Integrations.
  • Select NinjaOne from the list.

    If you're running on a Hudu version before 2.1.5.15, you'll need to select create integration.

    Ninja recently changed to the V2 version of their API. If you were using Hudu and Ninja together before Hudu 2.1.5.13, you will need to migrate.

In order to switch, you will need to delete your existing sync rules, create a new set of keys (following the below picture), and then re-set up your sync rules. Existing devices will be kept.

 

Obtaining the NinjaOne Information

  • Login to NinjaRMM and click on Configuration on the sidebar.
  • On the left-hand sidebar, click Integrations.
  • Click Client App IDs >> Add. Fill the fields in as shown.

    Redirect URI is not required but will show required until you un-click the 'authorization code' checkbox. Click the 'client credentials box' instead.

mceclip2.png

  • Copy the Client ID and Client Secret credentials into Hudu.
    • The secret key credential opens in a new window; only visible one time.
    • The client ID can be found in the list view of applications in Ninja after closing the client secret window.

    The Client ID is NOT the name of the application that you designated earlier; this is provided directly by Ninja.

image.png
 
  • Select either Oceania or the European region (if this applies to you).
  • Save the settings.

   Make sure to test the integration for a successful connection before continuing; do not continue on until you see a connection successful message display.

  • Start the sync. After inputting all settings and ensuring the connection was successful; start the sync to push initial data to Hudu from NinjaOne (this is required before moving on).

 

Matching Companies

Before your companies (and their corresponding data) from NinjaOne can be brought into Hudu, they must first be matched to companies that either already exists within your Hudu environment; OR to companies that you create now.
 

    Hudu recommends matching one company first, for testing purposes, to ensure that your information comes over correctly.

  • The first time your integration connection runs successfully, it will attempt to bring in companies from Ninja; these are then added to the Matched Companies List of that integration.
    • Navigate to the Hudu admin area >> Integrations >> and find NinjaOne from the list. Click into it.
    • It should now have a button that says Match Companies.
    • Go through the list of companies and either bulk create/match all OR decide to:
      • Match the company to an existing (already created) client in Hudu;
      • Create a matched client within Hudu from a Ninja company;
      • Leave unmatched, company (and corresponding data) will not be created/brought into Hudu.
  • Once you have matched your companies, you must re-run the integration import to fill in all the data for the newly matched/created companies.

assigning_matched_companies.png

 

Other Options

  • Choose which items, if any, you'd like to skip from being brought into Hudu.

Connect_NinjaRMM_-_OrganizedCo.png

 

Sort Rules

Sort rules allow you to select which device types (from Ninja) 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.
 
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.

Connect_Autotask_-_OrganizedCo.png

  • Save your settings and stop/start your integration sync again to reflect your changes.

 

FAQ

How often do integrations sync?

Answer: Native integrations will automatically re-sync (update) every 3 hours.
You can also use either the global or the card-specific re-sync features to refresh native integration syncs at any point.

Why is my integration taking a long time to finish?

Answer: If the sync has been loading for a significant amount of time (it can take up to 10 minutes), refresh the page. This should correct the forever loop. If this did not, try another re-sync.
Alternatively, ensure that there is no typo when inputting integration credentials.

Accidentally deleted an integration card; how do I get this back?

Answer: It should appear on subsequent re-syncs. If it is still not appearing, ensure that it has not been archived; and still exists in your sort rules.

Notes: Active integrations sync automatically every 3 hours; manual re-syncs can be performed either within an integrations’ settings page or by clicking the top right re-sync button.

My asset layouts aren't matching; what can I try?
Answer: If you cannot get your asset layouts to match, try deleting all integrated assets and checking your edit settings integration page to ensure there is no issue. Checking the logs can also help decipher potential errors.
Was this article helpful?
0 out of 0 found this helpful