N-able
Forward N-able N-central and N-sight alerts to AlertFlow via notification rules.
Supported products
| Product | Integration method |
|---|---|
| N-central (on-premises / cloud) | Notification profile → External Integration |
| N-sight (cloud RMM) | Alert Rule → HTTP Notification |
N-central Integration
Step 1 — Create the integration in AlertFlow
- Go to Integrations → New Integration.
- Select N-able (or Generic Webhook if N-able is not in the list).
- Name it (e.g., "N-central Production") and optionally assign a client.
- Copy the Webhook URL.
Step 2 — Create a Notification Profile in N-central
- In N-central, navigate to Administration → Notification Profiles.
- Click Add.
- Set Notification Method to HTTP Request (or External Notification).
- Configure the HTTP request:
| Field | Value |
|---|---|
| Method | POST |
| URL | Your AlertFlow Webhook URL |
| Content-Type | application/json |
| Body | See payload below |
Recommended body template (N-central variable syntax):
{
"title": "${NotificationName}",
"severity": "${Severity}",
"source": "n-central",
"description": "${Description}",
"labels": {
"device": "${DeviceName}",
"client": "${CustomerName}",
"check": "${ServiceDescription}"
}
}
- Save the notification profile.
Step 3 — Apply the profile to notification rules
- Navigate to Administration → Notification Rules (or Views → Notifications).
- Open or create a rule for the service states you want to forward.
- Under Notifications, add your new profile.
- Save the rule.
Step 4 — Test
Trigger a test condition in N-central (e.g., force a service to fail). The alert should appear in AlertFlow within seconds.
N-sight Integration
Step 1 — Create the integration in AlertFlow
Same as above — select Generic Webhook, copy the Webhook URL.
Step 2 — Configure an Alert Rule in N-sight
- In N-sight, go to Settings → Alert Manager (or Alerts → Alert Rules).
- Open or create an alert rule.
- Under Notification Actions, add an HTTP Notification action:
| Field | Value |
|---|---|
| Method | POST |
| URL | Your AlertFlow Webhook URL |
| Content-Type | application/json |
| Body | Paste the JSON template below |
Payload template for N-sight:
{
"title": "[N-sight] $CHECKNAME on $DEVICENAME",
"severity": "$SEVERITY",
"source": "n-sight",
"description": "$DESCRIPTION",
"labels": {
"device": "$DEVICENAME",
"client": "$CLIENTNAME",
"check": "$CHECKNAME"
}
}
- Set the Trigger condition (e.g., Check state changes to Failed).
- Save the rule.
Severity mapping for N-sight
Configure the following severity map in the AlertFlow integration's Field Mappings:
| N-sight Severity | AlertFlow Severity |
|---|---|
Critical | critical |
High | high |
Medium | medium |
Low | low |
Warning | medium |
Information | info |
Troubleshooting
| Symptom | Check |
|---|---|
| Alerts not arriving | Verify the webhook URL has no trailing space. Test with curl from the N-central/N-sight server to confirm network connectivity. |
ssl_error or TLS failure | Your AlertFlow domain uses TLS 1.2+. Ensure N-central's Java runtime supports TLS 1.2 (update if running an old on-premises version). |
All alerts show severity info | The severity field in the template is using a variable that doesn't resolve. Check the variable name against your N-central version's documentation. |
Connection refused | Confirm your firewall allows outbound HTTPS from the N-central server to app.yourdomain.com:443. |