Guide
Automate reactions with rules
Build event-driven rules: trigger → optional conditions → one or more actions.
The automation engine listens on every event ZentraLink emits and runs your rules when a trigger matches. Each rule is bounded by a per-hour cap so a runaway condition cannot fire thousands of times.
Step by step
- 1
Try a playbook first
Open Playbooks — SSL Expiry Protection, MX Drift Alert, DMARC Hygiene etc. are safe defaults you enable with one click.
- 2
Author a custom rule when you need more
Automations → New rule. Combine 8 condition shapes (criticality, environment, tag, severity, numeric thresholds) with any of 7 actions (notification, ticket, timeline event, webhook, report, recommendation, prepared change request).
- 3
Test before enabling
The Test button on each rule fires a synthetic event so you can verify the action without waiting for the real trigger.
- 4
Inspect runs
Each rule keeps a run log — success, failure and the input event are stored. Use this to debug or audit.
Tip: change_request.prepare actions create DRAFT change-requests only — they always flow through the normal approval workflow, never directly to DNS.