> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rallied.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# N-able N-central
> Connect N-able N-central so the agent can monitor devices, run scheduled tasks, manage custom properties, and generate reports across your customers.
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.ai exchanges the JWT for short-lived access and refresh tokens automatically, and re-authenticates with the stored JWT if the refresh token expires.
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.
In the Rallied.ai dashboard, navigate to **MSP Settings → Integrations**.
Find the N-able N-central card and click **Connect**. A credentials form appears.
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
Click **Save**. Rallied.ai calls `/api/auth/authenticate` with the JWT, stores the resulting access + refresh tokens, and the card shows **Connected** when complete.
Rallied.ai 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
| Tool | Description |
| -------------------------------------------------- | --------------------------------------------------------------------- |
| `n_central-list-service-orgs` | List service organizations in the N-central instance |
| `n_central-list-customers` | List customers, optionally filtered by service org |
| `n_central-create-customer` | Create a new customer |
| `n_central-list-sites` | List sites for a customer |
| `n_central-create-site` | Create a new site under a customer |
| `n_central-list-devices` | List managed devices, optionally filtered by customer or site |
| `n_central-get-device` | Get full details for a specific device |
| `n_central-get-device-assets` | Get hardware and software asset details for a device |
| `n_central-get-device-lifecycle-info` | Get lifecycle/warranty info for a device |
| `n_central-get-device-service-monitor-status` | Get service monitor status for a device |
| `n_central-get-device-custom-properties` | List custom properties on a device |
| `n_central-get-device-custom-property` | Get a single device custom property |
| `n_central-update-device-custom-property` | Update a device custom property |
| `n_central-list-org-custom-properties` | List custom properties on an organization |
| `n_central-update-org-custom-property` | Update an organization custom property |
| `n_central-list-active-issues` | List active issues across devices |
| `n_central-list-job-statuses` | List recent job statuses |
| `n_central-list-scheduled-tasks` | List scheduled tasks |
| `n_central-list-device-scheduled-tasks` | List scheduled tasks for a device |
| `n_central-run-direct-task` | Run a direct script/task on one or more devices with input parameters |
| `n_central-get-task` | Get a task definition |
| `n_central-get-task-status` | Get the status of a task execution |
| `n_central-get-task-details` | Get detailed task execution info |
| `n_central-generate-patch-report` | Generate a patch status report |
| `n_central-get-report` | Retrieve a generated report |
| `n_central-list-device-filters` | List configured device filters |
| `n_central-get-registration-token` | Get an N-central agent registration token |
| `n_central-list-users` | List N-central users |
| `n_central-create-user-role` | Create a new user role |
| `n_central-create-device-access-group` | Create a device access group |
| `n_central-api-get` / `-post` / `-put` / `-delete` | Generic API calls for endpoints without a typed tool |
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 [Policies](/dashboard/policies) for an overview of policy modes.