Automation
Ventryx Automation lets you replace manual, repetitive work with event-driven logic. Build triggers, rules, and notification flows that run automatically — without custom backend code.
Automation building blocks
| Component | What it does |
|---|---|
| Triggers | Detect conditions (events, schedules, thresholds) that start an automation |
| Rules Engine | Evaluate conditions and branch logic based on data values |
| Workflows | Define multi-step action sequences executed when triggered |
| Notifications | Send alerts to Slack, email, PagerDuty, or any webhook on automation events |
| Approvals | Gate automation steps on explicit human sign-off before proceeding |
Example: auto-escalation
A common automation pattern: when an error rate exceeds a threshold, automatically open an incident, notify the on-call team, and pause affected workflows until acknowledged.
Automation definition (YAML)
name: Error rate escalation
trigger:
type: metric_threshold
metric: error_rate
threshold: 0.05
window: 5m
rules:
- condition: error_rate > 0.10
action: notify
channel: pagerduty
severity: critical
- condition: error_rate > 0.05
action: notify
channel: slack
channel_id: "#incidents"
steps:
- type: pause_workflows
tag: production
- type: require_approval
approvers: ["[email protected]"]
- type: resume_workflows
tag: production
No-code and code-first
Automations can be built visually in the dashboard using the drag-and-drop builder, or defined as YAML/JSON files and deployed via the CLI or API — whichever fits your team's workflow. Both approaches produce the same underlying automation objects.