Connect N-able N-central to Current
Connect N-central once to bring its device inventory and active monitoring issues into your companies. Current reads data only. Device management, patch changes, remote commands and acknowledging alerts remain in N-central.
Before you connect
- 1Prepare a dedicated API userIn N-central, create an API user with read access to the customers you want to report on, then generate that user’s JSON web token. Use the JWT, not the short-lived access token returned by an API call.
- 2Check your serverUse a public HTTPS hostname on port 443 with a trusted certificate. N-central REST APIs require version 2023.9 or later, and individual endpoint availability still depends on the server version and permissions. Private network addresses cannot be connected.
- 3Test and save in CurrentOpen Integrations → Monitoring, security & lifecycle → N-able N-central → Manage. Enter the server address without /api or a sign-in path, paste the JWT, and choose Test connection.
Connect, map, then review
A workspace admin connects the feed in Integrations. After a successful test, the first sync is queued and starts within five minutes. Current reads in bounded passes and resumes from the last saved page, so a large estate may take several passes. A completed sync schedules the next refresh six hours later. Sync now queues work; it does not mean the data is already refreshed.
Open Manage and map each vendor customer to a Current company. Current matches exact, unique names automatically; ambiguous names stay unlinked. Review the matches. A manual mapping, unlink or Ignore choice is preserved across syncs. Saving a mapping immediately updates the company’s imported records.
Where the information appears
- ＋Company records show the mapped posture and an expandable list of devices or backup accounts. Account executives see only their authorized companies; external partner viewers cannot read the underlying integration mirrors.
- ＋Business reviews and AI company insights use the same company-scoped evidence. These are current snapshots, even when the review covers an earlier period.
- ＋Dashboards and reports use the shared metric catalog. Missing health is not a successful result; incomplete or stale data stays visible.
If a sync needs attention
| What you see | What to do |
|---|---|
| Credentials rejected | Check the dedicated API user and replace expired credentials in Manage. Never send tokens or passwords in a support message. |
| API access unavailable | Check the API user’s reporting permissions and, for N-central, the server version. Inventory can remain available while another endpoint is unavailable. |
| Waiting or retrying | Current saves progress and retries automatically. A vendor rate limit keeps its retry deadline even if Sync now is clicked again. |
| Sync error | Read the explanation in Manage. Earlier observations remain available with their dates. Persistent sync faults also reach Current’s super-admin Errors console through the existing error pipeline. |
| No company data | Check that the vendor customer is mapped to the intended company and that the first sync has completed. Unmapped records do not appear on a company profile. |
Rotate credentials or switch accounts
Replacing credentials for the same server or organization keeps company mappings. To switch to another server or Cove organization, disconnect first. Reconnecting to a different account resets this integration’s imported cache and mappings so reused vendor IDs cannot attach another organization’s data to an old company. Disconnecting stops future syncs and keeps existing observations until an account change replaces them.