FiveNines

Monitoring Workflows & Automation

Stop writing one-off scripts to handle alerts. Build monitoring automation visually - drag triggers, conditions, and actions onto a canvas, connect them, and publish. When a server goes down at 3 AM, your workflow handles the first 5 minutes of incident response before anyone wakes up.

Start Free - 5 Servers

No credit card required · 2-minute setup

How It Works

Choose Trigger

Host down, port unreachable, metric threshold, or cron job missed.

→

Add Conditions

Conditions to filter, delays to wait, rechecks to confirm the issue.

→

Configure Actions

Notify via Slack, Email, Discord, or Telegram. Create or close incidents.

→

Activate

Publish and it runs on schedule. Every execution logged with results.

Visual Drag-and-Drop Builder

A React-based canvas where you build workflows by connecting nodes. No YAML, no scripting, no learning a DSL. See the entire logic path at a glance.

10+ Trigger Types With Recheck

Host status, port checks, metric thresholds, and task monitors. Recheck nodes re-evaluate the trigger after a delay to filter transient spikes.

Automatic Incident Management

Create Incident and Close Incident nodes handle the full lifecycle. Incidents appear on your status page with a timeline from detection to resolution.

Visual Workflow Builder

The workflow builder is a full React application embedded in your dashboard. Drag nodes from the sidebar, drop them on the canvas, and connect them with edges. Each node has a configuration panel where you set thresholds, choose notification channels, or write condition logic.

The canvas shows you the entire execution path. Follow the flow from trigger to notification to incident creation. When a workflow runs, each node lights up with its result - passed, failed, or skipped.

Triggers, Conditions & Actions

Workflows combine three types of nodes:

Triggers: Host Status (up/down), Host Port (TCP reachability), Metric Threshold (CPU > 90% for 5 min), Task Monitor (cron job missed)
Logic: Conditions (if/else branching), Delays (wait N minutes), Recheck Trigger (re-evaluate before acting), Repeat While (loop until resolved)
Actions: Send notifications (Email, Slack, Discord, Telegram, Pushover, Webhooks), Create Incident, Close Incident

Each node type can be used multiple times in a workflow. Branch your logic to send different alerts to different teams based on severity.

How It Compares

Approach	Incident Creation	Delay / Recheck	Cost
Static Alerts			Varies
PagerDuty			$21+/user/mo
Datadog			$15+/host/mo
FiveNines	Built-in	Built-in	From €9/mo

Included on all plans

Unlimited workflows

Alerts via: Email Slack Discord Telegram Pushover Webhooks

Frequently Asked Questions

What trigger types are available?

FiveNines supports 4 trigger types: Host Status (up/down), Host Port (port reachability), Metric Threshold (CPU, memory, disk, etc. crossing a value), and Task Monitor (cron job missed or late). Each trigger can be combined with conditions and delays.

Can workflows create incidents automatically?

Yes. The Create Incident action node opens an incident with a full timeline. The Close Incident node resolves it when conditions return to normal. Incidents appear on your status page and can be tracked through resolution.

How does the recheck logic work?

The Recheck Trigger node re-evaluates the original trigger condition after a configurable delay. This prevents false positives from transient spikes. A CPU alert can require the threshold to be exceeded for 3 consecutive checks before firing.

Are workflows versioned?

Yes. Every time you publish a workflow, FiveNines creates a new version snapshot. You can view previous versions and the execution history for each. Running workflows always use the latest published version.

How many workflows can I create?

Unlimited workflows on all plans, including the free tier. There is no per-workflow charge.

Build your first monitoring workflow in 5 minutes

Start Free - 5 Servers

Free tier includes 5 servers - no credit card required