> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/n-central-integration.md).
# N-central Integration
Use N-ABLE N-central notification channels and service groups to create alerts in ilert.
Linking [N‑Central](https://www.n-able.com/products/n-central-rmm) to ilert enables MSPs to route technical alerts – such as device offline events or network issues – into tailored on-call workflows. These alerts trigger escalation paths and ensure rapid response and ticket creation for managed customer environments.
### In ilert: Create a N-central alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **N-central**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## Configure notifications in N-central
Login to N-ABLE N-central and navigate to the users menu.
Go ahead and click on the **email address** of the user for whose notifications you want to create alerts in ilert for. (We recommend creating a user just for this purpose, however that is not necessary).
In the user's edit view, click on the ***User Details*** tab and then on the **Notification Method** sub-tab.
Choose **Add** and create a new Third Party I**ntegration - HTTP** notification method.
Give it a proper name and paste the URL that you have copied ***from the new alert source*** that you have created in ilert from the steps above as **Target URL**.
Click on **Save** to create the new notification method.
Congratulations you have successfully connected N-central with ilert.
## Ensuring that notifications from N-central reach ilert
To make sure that N-central events will reach your ilert alert sources it is important to verify all required assignments of users in N-central.
* is your user part of an **Access Group** that is linked to the **Device**
* is your user assigned as **Primary Notification** of the **Notification Profile** (*Configuration -> Monitoring -> Notifications -> Choose Notification Profile of your choice e.g. Connectivity Failed -> Primary Notification -> Selected Recipients*)
## Acknowledgement and Resolving
To acknowledge and resolve N-central events in ilert you will need to add following notification templates.
1. On the sidebar navigate to **Administration -> Defaults -> Notification Templates**.
{% tabs %}
{% tab title="Acknowledgement" %}
1. Click on **Notification Acknowledgement**.
2. Scroll down to **HTTP MESSAGE TEMPLATE** and enter following template:
```
{{ActiveNotificationTriggerID}}
{{CustomerName}}
{{DeviceName}}
{{DeviceURI}}
{{ExternalCustomerID}}
{{AffectedService}}
{{TaskIdent}}
{{NcentralURI}}
{{QualitativeOldState}}
{{QualitativeNewState}}
{{TimeOfStateChange}}
{{ProbeURI}}
{{QuantitativeNewState()}}
{{ServiceOrganizationName}}
{{TimeOfNotification}}
{{AcknowledgementTime}}
{{AcknowledgementUser}}
{{AcknowledgementNote}}
```
{% endtab %}
{% tab title="Resolving" %}
1. Click on **Return To Normal Notification**.
2. Scroll down to **HTTP MESSAGE TEMPLATE** and enter following template:
```
{{ActiveNotificationTriggerID}}
{{CustomerName}}
{{DeviceName}}
{{DeviceURI}}
{{ExternalCustomerID}}
{{AffectedService}}
{{TaskIdent}}
{{NcentralURI}}
{{QualitativeOldState}}
{{QualitativeNewState}}
{{TimeOfStateChange}}
{{ProbeURI}}
{{QuantitativeNewState()}}
{{ServiceOrganizationName}}
{{TimeOfNotification}}
{{AcknowledgementTime}}
{{AcknowledgementUser}}
{{AcknowledgementNote}}
```
3. To activate resolving: On the sidebar navigate to **Configuration -> Monitoring -> Notifications**.
4. Now select a desired **Notification**.
5. Click on **Trigger Details** and either add or edit a trigger.
6. Select the **Notify on return to Normal** checkbox and save the trigger.
{% endtab %}
{% endtabs %}
## FAQ
### I am having issues creating an N-central user
You can find the official documentation [here](https://documentation.n-able.com/N-central/userguide/Content/User_Management/Role%20Based%20Permissions/role_based_permissions_create_user.htm)
### I am having issues creating an HTTP notification method for an N-central user
You can find the official documentation [here](https://documentation.n-able.com/N-central/userguide/Content/Further_Reading/API_Level_Integration/API_Integration_NotifReg.html)
### How can I test alerts?
If you navigate on to the **devices** overview of your assigned access groups or that are using your notification profile, you may click on one of the devices to edit them and select the specific device's ***service*** that relates to your Notification Profile, you can edit the check in the **Monitoring tab** and **reverse the check** - this will usually trigger a notification.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/integrations/inbound-integrations/n-central-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
