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

Notifications Overview

AlertFlow delivers alert notifications across six channels — SMS, voice call, email, Slack, Teams, and mobile push.

Supported channels

SMS

Delivered via Twilio. Reaches any phone number globally.

Voice Call

Automated voice call with a text-to-speech message. Escalates when SMS isn't enough.

Email

HTML email with full alert details and a one-click acknowledge button.

Slack

Posts to any Slack channel in your workspace. Supports rich formatting.

Microsoft Teams

Posts to a Teams channel via incoming webhook. Works with any Teams plan.

Mobile Push

Push notification to the AlertFlow mobile app (iOS and Android).

How notifications are sent

Notifications are sent by workflow Notify nodes. A single alert can trigger notifications to multiple channels simultaneously or sequentially — it depends on how your workflow is built.

Direct vs. on-call routing:

  • Direct — the Notify node sends to specific people or channels you name explicitly
  • On-call — the Notify node sends to whoever is currently on-call per your rotation schedule (recommended for after-hours escalation)

Notification log

Every notification attempt is logged in the Notification Log (accessible from the incident detail page and from Settings → Notification Log). The log shows:

  • Channel and destination
  • Delivery status (pending, sent, delivered, failed, acknowledged)
  • Provider message ID
  • Error details if failed
  • Timestamp

This is your first stop when debugging "why didn't I get the page?"

Acknowledgment from notification

Engineers can acknowledge alerts directly from the notification:

  • Email — one-click "Acknowledge" button
  • SMS — reply ACK (or ACK <alert-id> for specificity)
  • Voice call — press 1 during the call
  • Slack — click the Acknowledge button on the alert message

Channel delivery guarantees

AlertFlow does not guarantee delivery for channels that depend on third-party providers (Twilio, SendGrid, Slack, etc.). If a channel fails, the notification is logged with the provider error. Consider configuring a fallback channel to ensure coverage.

Fallback Numbers

Set a secondary number to try if the primary SMS or voice call fails.

Quiet Hours

Silence non-critical channels between midnight and 7 AM.

AI AssistantChannel Setup