N-able

Forward N-able N-central and N-sight alerts to AlertFlow via notification rules.

Supported products

ProductIntegration 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

  1. Go to Integrations → New Integration.
  2. Select N-able (or Generic Webhook if N-able is not in the list).
  3. Name it (e.g., "N-central Production") and optionally assign a client.
  4. Copy the Webhook URL.

Step 2 — Create a Notification Profile in N-central

  1. In N-central, navigate to Administration → Notification Profiles.
  2. Click Add.
  3. Set Notification Method to HTTP Request (or External Notification).
  4. Configure the HTTP request:
FieldValue
MethodPOST
URLYour AlertFlow Webhook URL
Content-Typeapplication/json
BodySee 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}"
  }
}
  1. Save the notification profile.

Step 3 — Apply the profile to notification rules

  1. Navigate to Administration → Notification Rules (or Views → Notifications).
  2. Open or create a rule for the service states you want to forward.
  3. Under Notifications, add your new profile.
  4. 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

  1. In N-sight, go to Settings → Alert Manager (or Alerts → Alert Rules).
  2. Open or create an alert rule.
  3. Under Notification Actions, add an HTTP Notification action:
FieldValue
MethodPOST
URLYour AlertFlow Webhook URL
Content-Typeapplication/json
BodyPaste 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"
  }
}
  1. Set the Trigger condition (e.g., Check state changes to Failed).
  2. Save the rule.

Severity mapping for N-sight

Configure the following severity map in the AlertFlow integration's Field Mappings:

N-sight SeverityAlertFlow Severity
Criticalcritical
Highhigh
Mediummedium
Lowlow
Warningmedium
Informationinfo

Troubleshooting

SymptomCheck
Alerts not arrivingVerify 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 failureYour 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 infoThe 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 refusedConfirm your firewall allows outbound HTTPS from the N-central server to app.yourdomain.com:443.