Skip to main content
Triggr works with N-central customers, sites, devices, custom properties, scripts, issues and users through the REST API, as a dedicated API-only user. You need N-central 2023.9 or later (2025.4 for patch comparison reports), reachable over HTTPS at a public address; if a firewall sits in front of it, allow Triggr’s IP addresses.

​
Set up N-central

1

Prepare a role and access groups

Pick a least-privilege role that can do in the UI what Triggr should do, and access groups that include every customer you’ll map; Triggr only sees customers and devices in them. Both are under Administration > User Management.
2

Create the API user

At your service organization level, not under a customer, go to Administration > User Management > Users and click Create User. Assign the role and access groups on the Role and Access Groups tabs, clear Use Two-Factor Authentication under User Details > User Information (and tick MFA Not Required if MFA is enforced), then click Save.
3

Generate the JSON Web Token

Open the user, click the API Access tab, tick API-Only User and click Generate JSON Web Token. Copy the token, then click OK and Save. Generating a new token revokes the old one. See N-able’s Create an API-only user.
4

Allow scripts through the API (optional)

In Configuration > Scheduled Tasks > Script/Software Repository, turn on Enable API for each script or Automation Policy Triggr should run. Its Repository ID is the itemId for Run Script or Automation Policy; pass a script’s command line as CommandLine, and an Automation Policy’s inputs by their Input Parameter names. See N-able’s Manage tasks and jobs.

​
Connect it in Triggr

1

Open the integration

Go to Integrations > N-able N-central and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the token and server

Paste the token into API Token (User-API JWT). In N-central Server URL, enter the final address you sign in at, such as https://ncentral.example.com, without /api (add a path only behind a reverse proxy). Turn on Allow insecure TLS for a self-signed or internal certificate, then click Save Configuration.
The N-able N-central configuration window with API Token (User-API JWT) and N-central Server URL fields and their help text, an Allow insecure TLS switch under Advanced, and a Save Configuration button.

​
Map your clients

On the Client Mapping card, click Apply 100% Matches, then choose the customer in Mapped to for anyone left. Triggr saves each match as the client’s ncentralCustomerId variable, which is also the customer’s org unit ID, so use it wherever an action asks for either. A client mapped to several customers gets comma-separated IDs.
The Client Mapping card with All, Mapped and Unmapped filters, Acme Corp mapped to Acme Corp with a 75% suggested mapping, and Globex unmapped with a Select ConnectWise Manage clients dropdown.

The Client Mapping card, shown here for ConnectWise Manage.

Allow insecure TLS covers workflow actions, not Client Mapping. If your server’s certificate isn’t publicly trusted, set each client’s ncentralCustomerId variable yourself: open the client in Clients, click Manage Variables on the Variables card, then New Variable. The ID is the customerId from List Customers.

​
Troubleshooting

Triggr couldn’t get a token from /api/auth/authenticate. For 401 or 403, check the token is current and the user is enabled, API-Only User and without two-factor authentication. For 404, check the server URL and version. For a redirect, use the server’s final address. If only Client Mapping fails and Allow insecure TLS is on, see Map your clients.
Enter N-central Server URL as https:// plus the host only, such as https://ncentral.example.com. Triggr adds /api itself and never sends the token over http://.
The API user’s password expired (every 90 days by default). Set a new one in N-central and, if calls still fail, generate a new token. See N-able’s known issues.
Add them to an access group assigned to the API user, then click Refresh on Client Mapping.
Give the user’s role the permission a technician would need. For scripts, also check Enable API is on.