Prerequisites
Before starting the integration setup, ensure you have:- Admin Access: Administrator access to your N-Central instance
- Role-Based Permissions: Ability to create users and configure role-based permissions
- API User Creation: Permissions to create dedicated API users
Setup Guide
1
Create API user
Set up a dedicated API user account with appropriate role-based permissions:
- Navigate to Administration → User Management
- Click Create User or Add New User
- Configure the user details:
- Username: Use a descriptive name (e.g.,
neo_agent_api) - Email: Set to a monitored email for notifications
- Authentication: Configure for API access
- Username: Use a descriptive name (e.g.,
2
Configure role-based permissions
Assign the necessary permissions for monitoring, alerting, and automation tasks:
- Navigate to Administration → Role Based Permissions
- Create a new role or modify an existing one for Neo Agent
- Enable the following permission categories:
- Devices: Read and manage device information
- Automation: Execute scripts and automation policies
- Monitoring: Access monitoring data and alerts
- Alerts: View and manage alerts
3
Generate API credentials
Generate the authentication credentials for your API user:
- Access the API user settings
- Generate an API key or JWT token based on your N-Central configuration
- Securely store the credentials
Note down the API endpoint URL for your N-Central instance as you’ll need this during configuration.
4
Configure in Neo Agent
Navigate to the Neo Agent Dashboard and select N-Able N-Central from the RMM integrations.Enter your credentials:
- API URL: Your N-Central instance URL
- API Key/Token: The authentication credential generated
- Additional settings: Any region or instance-specific configuration
5
Test and save
Neo Agent will validate your credentials and establish the connection.
A successful connection allows Neo to access your devices, automation policies, and monitoring data.
Role-Based Permissions Reference
Configure the following permissions for the Neo Agent API user:Device Management
| Permission | Level | Purpose |
|---|---|---|
| View Devices | All | Access device inventory and details |
| Manage Devices | All | Execute management tasks on devices |
| Device Properties | Read/Write | Access and update device properties |
Automation
| Permission | Level | Purpose |
|---|---|---|
| View Scripts | All | Browse available automation scripts |
| Execute Scripts | All | Run scripts on managed devices |
| Automation Policies | Read | Access automation policy configurations |
Monitoring and Alerts
| Permission | Level | Purpose |
|---|---|---|
| View Monitoring | All | Access monitoring check results |
| View Alerts | All | Access active and historical alerts |
| Manage Alerts | All | Clear and acknowledge alerts |
Permission levels may vary based on your N-Central version. Consult the N-Central documentation for your specific version’s permission structure.
What Neo Can Do
With N-Able N-Central connected, Neo Agent can:Automation Policy Execution
Automation Policy Execution
- Browse available automation policies and scripts
- Execute automation on specific devices
- Monitor automation job status
- Take follow-up actions based on results
Device Management
Device Management
- Look up devices across your managed clients
- Access device details, status, and properties
- View software inventory and installed applications
- Identify devices related to tickets or end users
Monitoring and Alerts
Monitoring and Alerts
- Access real-time monitoring data
- Process and respond to alerts
- Clear alerts after successful remediation
- Correlate monitoring status with ticket context
Troubleshooting
Authentication Errors
Authentication Errors
- Verify the API credentials are entered correctly
- Check that the API user account is active
- Ensure the API URL is correct for your instance
- Confirm the authentication method matches your configuration
Permission Denied
Permission Denied
- Review the role-based permissions for your API user
- Ensure all required permission categories are enabled
- Check for any customer/site level permission restrictions
Devices or Scripts Not Visible
Devices or Scripts Not Visible
- Verify the API user has access to the relevant customers/sites
- Check device-level and script-level permissions
- Ensure automation policies are not restricted
External Resources
N-Able N-Central API Documentation
Official N-Able documentation for creating API users with role-based permissions.
