This integration uses the N-central REST API to read customers, sites, devices, device asset details and lifecycle information. It is for N-able N-central; it is not an N-sight RMM connection.
Create the API user
Use an N-central instance with the REST API available. Create a dedicated API-only user.
Assign a read-only API role and access groups covering the customers, sites and devices you intend to collect. An API user’s role and access groups both control what it can read.
Generate the user’s N-central User-API Token (JWT) and store it securely. This is the long-lived credential Lexful exchanges for access tokens; do not paste a short-lived access token instead.
Follow N-able’s API-only user guide and read-only API role permissions.
Connect in Lexful
Sign in to the intended Lexful account as an administrator. Open Platform → Integrations → Data sources.
Find N-able N-central 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 N-able N-central.
Lexful field | What to enter |
API URL | Your N-central REST root, including |
JWT Token | The N-central User-API Token generated for your API user. |
Lexful exchanges the JWT at the authentication endpoint and uses the returned access token for inventory reads.
Check the first sync
The connection test checks N-central server information after authentication. 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
Server information access does not prove access to every customer or device. Check the user’s role, access groups and JWT validity, plus whether the N-central server is reachable. Read-only inventory access is sufficient; do not grant device-management permissions just to troubleshoot a missing record.
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.