N-able N-central integration setup

N-central Required Version

The new REST API endpoints are only available on N-central with a version of 2023.9 or above. Contact your N-able Representative to be upgraded where applicable.

What does the N-able N-central integration do?

Our N-able N-central integration allows MSPs to seamlessly interact with N-central's powerful RMM capabilities through Rewst, facilitating device management, task automation, and efficient operational workflows.

Integration use cases

Automatically synchronize device and customer data with your Rewst workflows.
Execute and manage scheduled tasks directly from Rewst.
Run automated Powershell scripts remotely to maintain and configure devices.

Integration prerequisites

N-able N-central version 2023.9 or above
A dedicated API user created in N-able N-central
A JSON web token from N-able N-central
Powershell scripts configured for API access in N-able N-central
Defined organization variables in Rewst

Set up the N-able N-central integration

Set up steps in N-able N-central

Navigate to Administration > User Management > Users.
Click Create User to create a new user specifically for API access. Name the user something that will easily identify its purpose.
Assign appropriate permissions required for your automations On the Access Groups and Roles tabs.
1. Roles: Create a role under user management > roles for a full API user. Name it administrator and set all the properties to manage. A reference sheet can be found here under N-able API user permissions.
2. Access Groups: Set this to All.
Click the User Details tab. Click User Information.
Check MFA Not Required to on.
Click into the API Access tab.
Check API Only User to on.
Click Save.
Click Generate JSON Web Token.
Securely copy the generated API key. You’ll need this information for the next setup steps in Rewst.

Set up steps in Rewst

Navigate to Configuration > Integrations in the left side menu of your Rewst platform.
In the Integrations page, search for the N-able N-central integration.
Click on the integration tile to launch the Configuration setup page.
Fill out the form with the details you created:
1. API Key: The JSON Web Token generated on the API user you created
2. Base URL: The base URL of your N-able N-central environment e.g rewst.n-able.com if different from the resource server hostname.
Save the configuration. Rewst will do a quick validation of your input.

Beneath that integration authentication section you’ll see the following options:

Suggest Values: This option will attempt to generate mappings between Rewst organizations and child organizations in this integration.
Refresh Options: This will re-read the potential mapping options - both organizations and companies in N-able.
Save Mappings This will apply mapping configuration changes.

Running Powershell via RMM - Script Setup

In order to run Powershell on devices via the RMM, you must create the Script in your N-able repository and enable its access for use over the API, as per N-able Security Policies.

Navigate to Configuration > Scheduled Tasks > Script/Software Repository in N-able.
Click Add > Scripting.
Name the script Rewst (Powershell).
Enter a script description.
Download and upload the provided PS1 file.
Enable API Access for the script.
Note the Repository ID.
In Rewst, create an organization variable named nable_rewst_powershell_script_id with the Repository ID as its value.
Update your Powershell script's $rewst_base_url variable to match your Rewst Instance URL:

Rewst URL

Base URL

app.rewst.io

engine.rewst.io

app.pdx.rewst.io

engine.pdx.rewst.io

app.eu.rewst.io

engine.eu.rewst.io

app.rewst.eu

engine.rewst.eu

app.rewst.asia

engine.rewst.asia

645B

run-nable-powershell.ps1

The ORG Var is only currently required as there is no way to search for a script with the existing API Endpoints

Once imported, you must update your script's $rewst_base_url variable. Your Rewst Base URL will vary depending on which Rewst instance you are on. You must update the $rewst_base_url property in the script below to match your Rewst Instance. You can identify which instance you are on by the URL you use to access Rewst. Please use the following table as a guide to identify your Rewst Base URL

Test the Integration

Navigate to Automation > Workflows in Rewst.
Create a new workflow and name it with something short and descriptive, such as Test N-able Integration.
Add the action List Agents to the workflow builder canvas, by dragging it from the left pane.
Add a trigger to your test workflow by clicking . Name your trigger whatever you’d like.
Click into the trigger’s settings.
Toggle Enabled to on.
Set the Trigger Type to Core - Always Pass.
Click next to Integration Overrides. Add N-able N-central as your integration override.
In the Activate Trigger To Run For section, keep Selected Organization toggled on. Toggle All current and future managed organizations on, or choose just one or individually selected organizations from the Organizations drop-down selector.
Click Submit to save your trigger.
Click Publish to save your changes.
Click Test to run your workflow. Note that this will bring up a drop-down selector to choosing organizations.
Select your MSP level.
Click Test and confirm that the execution finishes without errors.
If the test for your MSP is successful, do the same test again. At this point in your steps, select a client organization instead, and ensure that it finishes with no errors.

Troubleshoot the N-able N-central integration

API Authentication Errors: Verify JSON Web Token permissions and validity.
Powershell Script Execution Issues: Check script API access permissions in N-able.

Got an idea for a new Integration? Rewst is constantly adding new integrations to our integrations page. Submit your idea or upvote existing ideas here in our Canny feedback collector.

Current Limitations

There is currently no way to identify a Domain Controller via the N-able REST API. You must manually set the hostname of the preferred DC. Do this using the organization variable form that was discussed during your onboarding. The end result will be an organizational variable called preferred_domain_controller and a value of the hostname of that client's DC.

N-able N-central actions and endpoints

For more on how actions work in Rewst, check out our introductory actions documentation here.

For detailed endpoint documentation, log in to your N-able account or view their API documentation here.