What You'll Need
- Access to retrieve NinjaOne API credentials.
- Admin or super-admin user role within Hudu.
At any time, you can come back to your Hudu admin area >> Integrations >> NinjaOne to make changes to the integration.
Integration Features
-
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).
-
Locations.
- Pull locations from NinjaOne.
Use our Hudu Assist browser extension feature to bring the power of the Hudu interface into the tools your team is already using. For more information, visit our Hudu Assist article!
You can use Connected Fields to map information from this integration into Hudu custom fields. This allows data to appear in list views and be fully searchable across your account. Learn more →
What Hudu needs from NinjaOne
- Client ID.
- Client Secret.
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.
Obtaining the NinjaOne Information
- Login to NinjaRMM and click on Administration on the sidebar.
- On the left-hand sidebar, click Apps.
- Select API
- 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.
Setting up the Integration in Hudu
Step 1. Connect to Ninja
- 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.
- Select either the US2, European, Oceania or Canadian region (if this applies to you).
If you select a region when not required, the test connection will fail. If your connection test is not connecting, consider checking to see if this option was enabled.
- If you utilize NinjaOne's SSO, enter your SSO URL to allow the "Launch" button from Hudu to NinjaOne to direct to the correct URL.
- Select Skip Importing Devices (optional)
-
Select Default Asset Layouts
Choose asset layouts (must be active asset layouts) from the list to designate as the default asset layouts
They store information that is pulled in but not explicitly mapped to another asset layout
-
The NinjaOne integration requires two default asset layouts:
Configurations
Locations
If you don't see/have not created any asset layouts yet, you’ll need to create these. Visit Asset layouts for additional information!
- Select any additional options:
- Auto-update names of Assets - If name is changed in Ninja, 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 Ninja
- 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 NinjaOne companies
Make sure to test the integration for a successful connection before continuing; do not continue on until you see a connection successful message display.
Step 3. Match Ninja Companies
-
Before companies from Ninja 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 client first for testing to ensure data imports correctly
-
When the integration runs successfully for the first time:
Companies from Ninja are imported
They appear in the Matched Companies List for the integration
Navigate to Hudu Admin → Integrations → NinjaOne
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 a Ninja company
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. Choose where Ninja assets will fill to
-
Add Sort Rules
Sort Rules determine how data types from Ninja are mapped to asset layouts in Hudu
They let you define specific rules that control where each asset type is placed
Any asset types imported without an assigned Sort Rule will automatically be placed into the default asset layout
Asset layouts used for Sort Rules can be created ahead of time in the Hudu admin area (Admin → Asset Layouts) and must be marked as Active
You can also create new asset layouts directly from this section if needed.
Save the Settings
Step 5. Test connection and run a final sync
- Test the connection from the integration overview page
- If successful, stop and restart the sync to bring in Ninja devices and locations
FAQ
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.
Answer: If the NinjaOne sync has been loading for a significant amount of time (it can take up to 10 minutes), follow the steps below:
-
- Test the connection to ensure Hudu and NinjaOne are communicating correctly.
- Verify your NinjaOne credentials.
- Refresh the page (while a sync is actively running).
- Stop the sync and restart the sync.
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.