Site list with status controls
The OpsFlow dashboard lists monitored websites with status dots and basic management actions. The active UI supports adding sites, deleting sites, and pausing or resuming monitoring.
Operations monitoring
OpsFlow
Monitor uptime, latency, and alert rules before small outages become client problems.
OpsFlow is the active website monitoring module inside ConnectEngine OS. It checks active sites every 15 minutes, stores uptime and latency history, respects per-site alert settings, and sends Telegram alerts when configured rules are crossed. The goal is simple operational visibility: know whether a site is reachable, too slow, paused, or already in an alert state.
Focused on basic monitoring today, with reports and analytics kept out of the current promise.
Core workflow
A quiet monitoring layer for sites that need to stay reachable.
Site detail and uptime windows
Each site has a detail page with 24-hour, 7-day, and 30-day uptime percentages, alert history, and a timeline of recorded checks for quick incident review.
15-minute uptime checks
The n8n uptime workflow runs every 15 minutes, checks active sites with HEAD first and GET as fallback, records results, and evaluates alert rules after each run.
Latency threshold tracking
OpsFlow stores check data and uses latency thresholds as part of per-site alert configuration, so slow responses can be treated differently from full downtime.
Per-site alert rules and quiet hours
Alert configuration includes latency threshold, consecutive failures, quiet hours, and notification toggle. A site can wait for a meaningful failure pattern before alerting.
Telegram alerts
The current implementation sends Telegram notifications through the ConnectEngine alerts bot and respects per-site quiet hours when alert rules trigger.
How it works
From adding a site to getting a useful alert.
Add the site
Create the monitored website in OpsFlow, confirm it appears in the site list, and keep it active unless you intentionally pause checks.
Set thresholds
Configure latency threshold, consecutive failures, quiet hours, and notification status so alerts match the way that site should be watched.
Review checks and alerts
Use the detail page to inspect uptime percentages, recent check timelines, alert history, and the first successful stored check after setup.
Integrations
Simple monitoring backed by the existing automation stack.
n8nTelegramSupabaseConnectEngine alerts bot
FAQ
Common OpsFlow questions.
What is the check frequency?
The active uptime workflow runs every 15 minutes. It checks active sites, records the result, and evaluates per-site alert rules.
Do quiet hours work per site?
Yes. The documented alert_config is per site and includes quiet hours. Alerts may appear delayed when they are intentionally suppressed during that window.
Can I get alerts via Slack or WhatsApp?
The active documented delivery path is Telegram. Broader channel routing is referenced in the notification architecture, but this landing page only promises the live Telegram path.
Is OpsFlow a full analytics product?
No. The active module is basic monitoring: site list, detail page, uptime percentages, check timeline, alert rules, and Telegram notifications. GA4 analytics and weekly reports are not live customer functionality.
Will one slow response always trigger an alert?
Not necessarily. Alert rules can require consecutive failures, and quiet hours can suppress delivery, so OpsFlow is designed to reduce noise rather than alert on every brief fluctuation.
More modules
Pair monitoring with the growth workflows around it.
Ready to try OpsFlow?
Join the waitlist for early access to ConnectEngine OS monitoring, alert rules, and the broader automation dashboard around your sites.