Skip to main content
Connect N-able N-central so the agent can query devices, run scheduled tasks, manage org and device custom properties, view active issues, and generate patch reports across every customer (service organization) in your N-central instance.
N-central is configured in MSP Settings → Integrations.

​
How to connect

N-central uses a long-lived JWT token generated from the N-central UI. Rallied exchanges the JWT for short-lived access and refresh tokens automatically, and re-authenticates with the stored JWT if the refresh token expires.
1

Generate a JWT token in N-central

Sign in to your N-central instance as a user with API access. Open your User Profile → API Access (or Administration → User Management) and generate a JWT token.The JWT lives until the user’s password expires (default 90 days) or the token is explicitly regenerated, so pick a service account whose password rotation cadence you control.
2

Open MSP Integrations

In Rallied, go to MSP Settings → Integrations.
3

Connect N-able N-central

Find the N-able N-central card and click Connect. A credentials form appears.
4

Enter your credentials

Fill in:
  • Instance URL — your N-central server, e.g. https://yourserver.n-able.com (no trailing slash; HTTPS required)
  • JWT Token — the JWT you generated in step 1
5

Save and confirm

Click Save. Rallied calls /api/auth/authenticate with the JWT, stores the resulting access + refresh tokens, and the card shows Connected when complete.
Rallied stores the JWT permanently and uses it to re-authenticate if the refresh token expires (typically every 25h). If you regenerate the JWT in N-central or the source user’s password expires, the connection will eventually fail. Reconnect from MSP Settings → Integrations with a fresh JWT.

​
How the agent uses it

When a request involves a customer or device managed in N-central (“what’s wrong with the file server at Acme?”, “push the cleanup script to all of Globex’s workstations tonight”, “give me a patch report for last week”), the agent typically:
  1. Resolves the customer with n_central-list-service-orgs or n_central-list-customers.
  2. Finds the device with n_central-list-devices (and n_central-get-device for full asset info).
  3. Pulls health data from n_central-list-active-issues, n_central-get-device-service-monitor-status, n_central-get-device-lifecycle-info, or n_central-get-device-assets.
  4. Runs remediation via n_central-run-direct-task (a pre-defined N-central script with input parameters) and follows up with n_central-get-task-status / n_central-get-task.
  5. For reporting, it kicks off n_central-generate-patch-report and retrieves it with n_central-get-report.
For anything not covered by a typed tool, the agent can fall back to raw API calls via n_central-api-get, -post, -put, and -delete.

​
Tools

Default policies are seeded per tool — read-only lookups default to auto, mutations and task runs default to approval needed. Tune them on the N-able N-central integration detail page.

​
Policies

N-central is an integration. Per-tool policies are configured on the N-able N-central integration detail page (open it from MSP Settings → Integrations). See Approval settings for an overview.