The NinjaOne integration collects organizations, locations, contacts and detailed device inventory. It also reads device health, installed software/antivirus, hardware components and installed software/OS patch information. These source datasets do not all become separate asset types in Lexful.
Create the NinjaOne application
In NinjaOne’s API application settings, create an application with API Services as its platform.
Enable the Client Credentials grant and Monitoring scope. Lexful requests
monitoring; Management or Control permissions are not required for these inventory reads.Securely retain the Client ID and Client Secret. Confirm the host for your NinjaOne region.
Use NinjaOne’s machine-to-machine application guide and Client Credentials reference. This flow does not require a user sign-in redirect.
Connect in Lexful
Sign in to the intended Lexful account as an administrator. Open Platform → Integrations → Data sources.
Find NinjaOne and choose Connect. If it is already connected, open the existing connection instead.
Enter the values below. Where the form displays https:// separately, enter the hostname and path without repeating it.
Select Test Connection. Resolve any error, then select Connect NinjaOne.
Lexful field | What to enter |
Client Id / Client Secret | Your API Services application’s credentials. |
API URL | Your NinjaOne regional API host, for example |
Auth Url | The matching regional host. Lexful uses |
Scope |
|
Check the first sync
The connection test checks the NinjaOne organization list. It does not prove that every source table is readable or that records have reached your documentation.
Open the connection’s Sync logs and check that the relevant source tables finish successfully.
Review Mapping for source types, statuses and other values. Save any changes.
Open Data sync → Configure sync, save your primary organization, enable the customers you want, and review the available record filters.
Run Sync now on Data sync, review the result, then check a sample organization and its records.
Configure mappings and data sync explains these steps in detail. Collection from the provider and syncing records into Lexful are separate stages.
If something is missing
If the token request fails, verify Client Credentials and Monitoring are enabled, and both URLs use the correct region. If collection succeeds but a contact or device is absent in Lexful, check customer matching and sync filters. This integration does not provide remote control or write changes to NinjaOne.
A successful test followed by a failed table usually means that table needs additional read access. A successful collection followed by missing records usually means organization matching, customer selection or record filters need review. Include the provider, failed table and visible error when contacting support; never include credentials.