SolarWinds

Forward SolarWinds Orion and SolarWinds RMM alerts to AlertFlow via trigger actions.

Supported products

ProductIntegration method
SolarWinds Orion (NPM, SAM, etc.)Alert → Execute an HTTP Request action
SolarWinds RMM (N-able legacy)See N-able guide

SolarWinds Orion Integration

Step 1 — Create the integration in AlertFlow

  1. Go to Integrations → New Integration.
  2. Select SolarWinds (or Generic Webhook if not listed).
  3. Name it and optionally assign a client.
  4. Copy the Webhook URL.

Step 2 — Create an Alert in SolarWinds Orion

  1. In the Orion web console, navigate to Alerts & Activity → Alerts.
  2. Click Manage Alerts, then Add New Alert.
  3. Configure the alert trigger conditions (node status, CPU threshold, etc.).

Step 3 — Add the HTTP Request Trigger Action

  1. In the alert wizard, click Trigger Actions.
  2. Click Add Action and select Execute an HTTP Request.
  3. Configure the request:
FieldValue
URLYour AlertFlow Webhook URL
MethodPOST
EncodingJSON
BodySee template below
AuthenticationNone (AlertFlow authenticates by token in the URL)

Body template (uses SolarWinds macro variables):

{
  "title": "${NodeName} — ${AlertName}",
  "severity": "${Severity}",
  "source": "solarwinds-orion",
  "description": "${AlertDescription}",
  "labels": {
    "node": "${NodeName}",
    "ip": "${IP}",
    "location": "${City}",
    "trigger_time": "${TriggerTime}"
  }
}
  1. Click Test to verify the request reaches AlertFlow.
  2. Save the action, then click Next through the wizard and save the alert.

Step 4 — Add a Reset Action (optional — auto-resolve)

To automatically resolve the alert in AlertFlow when the condition clears:

  1. In the same alert, go to Reset Actions.
  2. Add a new Execute an HTTP Request action with the same URL but a different body:
{
  "title": "${NodeName} — ${AlertName}",
  "severity": "${Severity}",
  "status": "resolved",
  "source": "solarwinds-orion",
  "fingerprint": "${NodeName}-${AlertName}"
}
Tip

The fingerprint field must match between the trigger and reset payloads for auto-resolve to work. Using ${NodeName}-${AlertName} is a reliable combination.

Severity mapping for Orion

Configure this in the AlertFlow integration's Field Mappings → Severity Map:

SolarWinds SeverityAlertFlow Severity
Criticalcritical
Highhigh
Mediummedium
Lowlow
Informationalinfo
Noticeinfo

Troubleshooting

SymptomCheck
HTTP action doesn't fireVerify Orion can reach app.yourdomain.com:443. Check Orion → Admin → Log Viewer for HTTP action errors.
Alert arrives with no node infoSome macro variables are only available in certain alert templates. Verify the variable names against your Orion version.
SSL/TLS Handshake FailedOrion's HTTP action respects the system's Windows certificate store. Import the AlertFlow domain's TLS chain if using a private CA.
Duplicate alerts for same nodeAdd a fingerprint field to the trigger body: "fingerprint": "${NodeName}-${AlertName}". This deduplicates flapping conditions.