How to connect
N-central uses a long-lived JWT token that you generate in the N-central UI. Rallied exchanges the JWT for short-lived access and refresh tokens.1
Generate a JWT token in N-central
In N-central, go to Administration → User Management and select the user for API access, or create a dedicated API user. Give it permissions for the devices and customers you want the agent to manage. On the API Access tab, click Generate JSON Web Token and copy it.The JWT lasts until the user’s password expires (default 90 days) or someone regenerates the token. Use a service account whose password rotation you control.
2
Open the N-able N-central card
In Rallied, go to Settings → Integrations, find the N-able N-central card, and click Connect.
3
Enter your credentials
4
Connect and confirm
Click Connect. Rallied exchanges the JWT for access and refresh tokens. The card shows Connected when complete.
Rallied stores the JWT and uses it to re-authenticate when the refresh token expires, typically every 25 hours. If you regenerate the JWT or the user’s password expires, the connection eventually fails. Update the connection with a fresh JWT.
How the agent uses it
For a request like “what’s wrong with the file server at Acme?”, the agent resolves the customer, finds the device, and pulls its health data. It remediates by running a pre-defined N-central script, and it can generate patch reports. For anything without a typed tool, it falls back to raw API calls.Tools
Each tool has its own default policy. Read-only lookups default to Auto. Writes and task runs default to Approval needed. You can change them on the N-able N-central Policies tab under Settings → Integrations.
Related
- Approval settings for how Auto, Approval needed and Disabled work
- Execute Mode for how approvals play out once a client is live
- Workflows to tell the agent how to handle common requests
- Integrations to update credentials or disconnect N-central