NinjaOne

The NinjaOne RMM integration automatically syncs key data from NinjaOne into Hudu. It brings over device configurations, location information, and NinjaOne custom fields, helping keep documentation accurate and up to date without manual effort.

Before setting up your NinjaOne integration, please read over our Understanding Integrations article to learn basic concepts and useful tips.

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

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).
    • Skip syncing specific device types you don't want brought into Hudu.
  • Locations.
    • Pull locations from NinjaOne.
  • Custom fields.
    • Map NinjaOne device and location custom fields onto Hudu fields with Connected Fields.

    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, including custom fields you've created in NinjaOne. 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.

Obtaining the NinjaOne Information

  • Log in to NinjaOne and click Administration on the sidebar.
  • On the left-hand sidebar, click Apps.
  • Select API.
  • Click Client App IDs → Add. Fill in the fields as shown.

    Redirect URI is not required, but it will show as required until you uncheck the Authorization Code checkbox. Check the Client Credentials box instead.

    If your organization uses NinjaOne's FedRAMP environment, log in to your FedRAMP NinjaOne instance to create the client app. Credentials created in a commercial NinjaOne instance will not work with the FedRAMP endpoint.

Ninja_no_management.png

Setting up the Integration in Hudu

Step 1. Connect to Ninja
  • Copy the Client ID and Client Secret credentials into Hudu.
    • The client secret opens in a new window and is 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 you designated earlier; it is provided directly by Ninja.
image.png
  • Under Ninja endpoint, select the endpoint that matches where your NinjaOne instance is hosted:
    • US (default)
    • US2
    • European
    • Oceania
    • Canada
    • FedRAMP (for organizations using NinjaOne's FedRAMP environment)

    The endpoint must match the NinjaOne instance your credentials were created in. If your connection test is not connecting, confirm the selected endpoint matches the URL you use to log in to NinjaOne.

  • If you use NinjaOne's SSO, enter your SSO URL so the Launch button from Hudu to NinjaOne directs to the correct URL.

ninja_sso_url.png

  • 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 or 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 a name is changed in Ninja, it will automatically be updated in Hudu.
    • Do not update basic company details - Prevents company details from being changed in Hudu when 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 until you see a connection successful message.
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.

syncro_matched_companies.png

Step 4. Skip NinjaOne device types (optional)
  • Once an initial sync has been run, the NinjaOne device types in your account will appear under Skip the following NinjaOne device types.
  • Check any device types you don't want brought into Hudu (for example, WINDOWS_SERVER or NMS_PRINTER).
  • Devices of the checked types will be skipped starting with the next sync; all other device types will continue to sync.

    Skip Importing Devices in Step 1 stops all devices from syncing. Use the device type list instead if you only want to exclude certain types.

Step 5. Choose where Ninja data 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 6. 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.

NinjaOne custom fields

NinjaOne custom fields can be mapped onto Hudu fields with Connected Fields. Hudu discovers them during a device or location sync, and they then show up in the integration data point list.

Map a NinjaOne custom field to a Text, Rich Text, or Copyable Text field. NinjaOne custom fields are not listed on other Hudu field types, including Date, Checkbox, Number, and Phone.

    New custom fields in NinjaOne have their API permission set to None by default. Change it to at least Read Only and re-sync, or the field will not come through to Hudu.

    The asset layout must be a NinjaOne sync location (a default layout or a sort rule), or the source dropdowns will not appear.

Connect a custom field
  1. In NinjaOne, open the custom field and confirm it is active.
  2. Under the field's permissions, set API to Read Only or Read/Write. New fields default to None, which keeps the field out of Hudu.
  3. Under Inheritance, check Location. Device fields are available on layouts that receive NinjaOne devices, and Location fields are available on layouts that receive NinjaOne locations. A field set for both can be connected in each place. Organization-only fields are not synced.
  4. Run a NinjaOne sync. Hudu registers the fields on that sync.
  5. Edit the asset layout, open the field, choose NinjaOne under Sources, and select the custom field.
  6. Run the sync again. The value fills on that sync and is refreshed on each sync after it.
    A value you type in Hudu is overwritten on the next sync. Changes made in Hudu are not written back to NinjaOne.

A value stored only on the location syncs to the location asset. Hudu does not copy that inherited value onto the device.

    Visit Connected Fields for additional information on turning on a source and showing the value in the asset table.

How each field type syncs

Every custom field value is stored as text.

NinjaOne type What you see in Hudu
Text, Multi-line, Email, Phone, URL, IP Address The value as entered in NinjaOne
Integer, Decimal The number, as text
Checkbox true or false
Drop-down The selected option
Multi-select The selected options, separated by commas
Date, Date/Time The raw timestamp NinjaOne sends, in milliseconds. A date displays as a number such as 1792173600000, not as a calendar date
WYSIWYG The HTML from NinjaOne. Connect it to a Rich Text field to keep the formatting; a Text field shows the markup
Device, organization, or location dropdowns and multi-selects These can sync blank, or as an identifier, rather than the device, organization, or location name
Attachment Not listed. File attachments are not synced
Secure Not supported. NinjaOne does not send the stored secret to Hudu. If a Secure field is listed, the asset shows NinjaOne's placeholder (such as SECURE_VALUE or SECURE_VALUE_PLACEHOLDER followed by an ID), not the real value
TOTP Not a supported type. Do not rely on the synced value
The field is missing from the list

Check the following:

  • The layout is not a NinjaOne sync location, so the source dropdowns are hidden.
  • The Hudu field is not Text, Rich Text, or Copyable Text.
  • No sync has run since the field was created in NinjaOne.
  • In NinjaOne, the API permission is still None (the default for new fields), or the field is inactive.
  • Location is not checked under Inheritance in NinjaOne.
  • The field's scope does not match the layout. A Device field does not appear on the location layout, and a Location field does not appear on a device layout.
  • The field is scoped only to the organization.

FAQ

How often do integrations sync?

Answer: Native integrations 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.

How do I connect to NinjaOne's FedRAMP environment?

Answer: Create your client app in your FedRAMP NinjaOne instance, then enter the Client ID and Client Secret in Hudu and select FedRAMP under Ninja endpoint. Save the settings and test the connection.

Can I stop certain types of devices from syncing?

Answer: Yes. After an initial sync, check the device types you want to skip under Skip the following NinjaOne device types in the integration settings and save. Those types will not be synced on the next and future syncs. Devices that already synced before a type was skipped will remain in Hudu and can be archived manually.

Why is my integration taking a long time to finish?

Answer: A NinjaOne sync can take up to 10 minutes. If it has been loading longer than that, 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 it.
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 integration's settings page or by clicking the top right re-sync button.

Related to

Was this article helpful?
0 out of 1 found this helpful