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

Channel Setup

Configure each notification channel for your team members.

SMS

SMS is delivered via Twilio to any phone number globally. No per-member configuration is needed beyond adding a phone number.

Setup:

  1. Go to Settings → Team Members.
  2. Click a team member and add their Phone number in E.164 format: +15551234567.
  3. Toggle Notify via SMS on.

In workflows:

  • Select SMS as the channel in a Notify node
  • Choose specific team members, a role (e.g., "all admins"), or the current On-call engineer

Acknowledge via SMS: Reply ACK to any AlertFlow SMS. If you have multiple firing alerts, reply ACK <alert-id> to acknowledge a specific one.

Voice Call

Voice calls use text-to-speech to read the alert title and severity. The engineer presses 1 to acknowledge or 9 to escalate immediately.

Setup: Same as SMS — requires a phone number on the team member's profile.

In workflows:

  • Select Voice as the channel
  • Optionally set a Fallback phone (see Fallback Numbers)

Cost note: Voice calls consume more notification credits than SMS. Reserve them for critical, time-sensitive escalations.

Email

Email is delivered via SendGrid with an HTML template that includes:

  • Alert title, severity, and status badge
  • Full description and labels
  • One-click Acknowledge button (signed, expires in 24 hours)
  • Link to the alert detail in the dashboard

Setup: Each team member needs a verified email address (set during sign-up).

In workflows:

  • Select Email as the channel
  • Recipients can be specific team members or roles

Tip: For high-volume environments, use email only for non-critical alerts (medium/low). Reserve SMS/voice for critical.

Slack

AlertFlow posts rich messages to a Slack channel, including severity color coding, labels, and an Acknowledge button.

Setup:

  1. 1
    Connect your Slack workspace

    Go to Settings → Integrations → Slack and click Connect to Slack. Authorize AlertFlow in the OAuth flow.

  2. 2
    Choose the default channel

    After connecting, select the default Slack channel for alert notifications (e.g., #alerts).

  3. 3
    Use in workflows

    In a Notify node, select Slack and choose the channel. You can use different channels per workflow — #critical-alerts, #client-acme, etc.

Message format:

🔴 [CRITICAL] High CPU on WEB-01
Source: kaseya-vsa   Client: Acme Corp
Labels: host=WEB-01, env=production

[Acknowledge]  [View in AlertFlow]

Microsoft Teams

AlertFlow sends messages to a Teams channel via an Incoming Webhook connector.

Setup:

  1. 1
    Create an Incoming Webhook in Teams
    1. In Teams, open the channel where you want alerts.
    2. Click ... next to the channel name → Manage Channel → Connectors.
    3. Search for Incoming Webhook and click Configure.
    4. Name it AlertFlow and optionally upload the AlertFlow logo.
    5. Copy the webhook URL.
  2. 2
    Add the webhook URL to AlertFlow

    Go to Settings → Integrations → Microsoft Teams and paste the webhook URL.

  3. 3
    Use in workflows

    Select Teams as the channel in a Notify node.

Mobile Push

Mobile push requires the AlertFlow mobile app (iOS or Android). Push notifications appear instantly with the alert title and severity.

Setup:

  1. Download the AlertFlow app (App Store / Google Play).
  2. Sign in with your AlertFlow account.
  3. Enable push notifications when prompted.
  4. In the dashboard, go to Settings → Profile → Push Notifications and confirm the device is registered.

In workflows:

  • Select Push (App Push) as the channel
  • Recipients must have the mobile app installed and notifications enabled

Behavior:

  • Push notifications bypass quiet hours by default (override in Settings)
  • Tapping the notification opens the alert detail in the app

Per-user notification preferences

Each team member can override their default notification preferences:

  1. Go to Settings → Profile → Notifications.
  2. Toggle each channel on or off.
  3. Set Quiet Hours to pause non-urgent channels overnight.

These preferences apply when a workflow routes to a team member by role or on-call status. Workflows that target a specific channel (e.g., "always SMS this number") ignore user preferences.

Notifications OverviewFallback Numbers