Put your network on autopilot
Build rules that react to what's actually happening — a router going offline, a subscription expiring, a fleet nearing its quota — and take real action, not just alerts.
React to what your network is doing
Twelve triggers span routers, vouchers, subscriptions and platform events. Add threshold conditions so a rule only fires when it truly matters.
- 12 triggers: router offline/health, voucher & subscription lifecycle, low quota, backups, SLA and more
- Threshold conditions to avoid noisy alerts
- Run-now with an impact preview before anything happens
- Full execution history with per-run timelines
Not just alerts — actions
Beyond in-app and email notifications, a rule can call a signed developer webhook or push a RouterOS configuration template to the affected devices.
- In-app and email notifications
- HMAC-signed developer webhooks
- Push a config template as an action
- Every run recorded, re-runnable on failure
A real automation engine
Questions, answered
What can trigger an automation?
Router offline and health checks, voucher and subscription lifecycle events, low quota, backups, SLA sampling, commission accrual and daily digests — twelve triggers in all.
Can automations change my routers?
Yes — a rule can push a RouterOS configuration template to the affected routers as an action, reusing the same deployment engine as manual config pushes, and it's gated by the same permissions.
Will I see what an automation did?
Every run is recorded with a timeline and log, and failed or skipped runs can be re-run.
Explore more of the platform
Automate the busywork
Spin up MD ConnectPro and connect your first router in minutes. Free to start, self-hosted or cloud.