AlertFlow
Browse docs
AlertFlow DocumentationQuickstartIntegrations OverviewGeneric WebhookKaseya VSAConnectWise ManageN-ableSolarWindsDattoWorkflow BuilderBuilder TutorialCondition LogicEscalation PatternsAI AssistantNotifications OverviewChannel SetupFallback NumbersQuiet HoursOn-Call SchedulesAPI ReferenceAuthenticationList AlertsGet AlertAcknowledge AlertResolve AlertBulk AcknowledgeList IncidentsGet IncidentList ClientsCreate ClientUpdate ClientDelete ClientList WorkflowsGet WorkflowList SchedulesGet ScheduleCurrent On-CallList IntegrationsCreate IntegrationUpdate IntegrationDelete IntegrationList Suppression WindowsCreate Suppression WindowUpdate Suppression WindowDelete Suppression WindowList UsersList API KeysCreate API KeyRevoke API KeyIngest WebhookFAQ

Integrations Overview

Connect any monitoring tool to AlertFlow in minutes using native integrations or the generic webhook.

How integrations work

Every integration in AlertFlow has three components:

  1. Ingest endpoint — a unique HTTPS URL (/api/inbound/webhook/<token>) that receives raw payloads from your tool via HTTP POST.
  2. Field mappings — rules that normalize the raw payload into AlertFlow's standard format: title, severity, status, clientName, labels.
  3. Integration type — determines which pre-built parser runs on the payload. Native types (Kaseya VSA, ConnectWise, etc.) require zero configuration.

Supported integrations

Generic Webhook

Works with any tool that can POST JSON. Full field mapping control.

Kaseya VSA

Native alarm ingest + outbound ticket creation.

ConnectWise Manage

Native alert ingest + service board ticket creation.

N-able

N-central and N-sight notification rules.

SolarWinds

Orion trigger action webhook setup.

Datto

Datto RMM and PSA (Autotask) webhook setup.

Creating an integration

  1. 1
    Navigate to Integrations

    In the AlertFlow dashboard, click Integrations in the left sidebar, then New Integration.

  2. 2
    Select a type

    Choose the integration type that matches your monitoring tool. If your tool isn't listed, use Generic Webhook.

  3. 3
    Name and optionally assign a client

    Give the integration a meaningful name (e.g., "Kaseya — Acme Corp"). Optionally assign it to a client — this populates clientName on every inbound alert automatically.

  4. 4
    Copy the Webhook URL

    After saving, copy the unique Webhook URL from the integration card. Paste this URL into your monitoring tool's notification/webhook settings.

  5. 5
    Test

    Use the Test button in the integration modal, or send a manual curl POST, to verify alerts are arriving.

Alert severity mapping

AlertFlow normalizes severity to five levels. Native integrations handle this automatically; for generic webhooks you configure the mapping.

AlertFlow severityCommon equivalents
criticalP1, Emergency, Fatal, Alarm
highP2, High, Error
mediumP3, Medium, Warning
lowP4, Low, Notice
infoP5, Info, Informational

Deduplication

AlertFlow deduplicates alerts using a fingerprint — a hash of title + source + organizationId. If a duplicate arrives while the original is still firing, it increments the dedupCount counter instead of creating a new alert. This prevents alert storms from filling the dashboard.

You can override the fingerprint by sending a fingerprint or dedup_key field in the payload.

Rate limits

Ingest endpoints accept up to 60 requests per minute per token. Bursts above this return 429 Too Many Requests. The Retry-After header tells you when to retry.

QuickstartGeneric Webhook