Automation
Automate your whole stack, end to end
Let rules do the routine work across every module. Pick a trigger from anywhere — a domain registered, a monitor down, a certificate expiring — narrow it with conditions, then run the actions you want. Every time the event fires, hands-free.
Free plan · No credit card · Build your first rule in 2 minutes
One trigger here, an action anywhere in your stack.
When this happens, do that — across your whole stack
Triggers come from every module: domains, DNS, servers, monitoring and certificates. Actions run on any of them, in the order you set. So a single rule can span your entire stack rather than being trapped in one tool.
- Triggers from every module — a domain registered, a monitor down, a cert expiring
- Actions on any module, run in the order you choose
- One rule can cross modules — an event here, an action there
Conditions, and a run history you can audit
Narrow any rule with conditions so it only fires when the details match — fewer than 7 days left, a specific tag, a particular monitor. Every run is recorded: what triggered it, which conditions passed and what each action did, so you can always see exactly why something happened.
- Conditions filter on the event’s own details, so rules stay precise
- Every run logged with its trigger, conditions and each action’s result
- Re-run or inspect any past run, and see what changed
Every run kept, with the reason it fired.
Start from a recipe — no code required
Begin with a ready-made recipe and adjust it, or build your own from scratch in a guided editor. No code is needed for the common jobs — but webhooks and a REST API are there when you want to reach a tool InfraNest doesn’t cover yet.
- A library of ready-made recipes for the usual jobs
- Build custom rules with no code, step by step
- Webhooks and a REST API when you need to go further
Everything else it handles
The parts that are only interesting when you need them.
Triggers across modules
Start a rule from any event in your stack — a domain registered, a zone drifted, a server unhealthy, a monitor down, a certificate expiring, and dozens more.
Actions across modules
Run one or more actions in order, on any module — apply a DNS template, open a maintenance window, resolve an incident, tag a domain, and more.
Conditions & filters
Fire only when the event’s own details match — a days-left threshold, a specific monitor, a tag — so a rule stays as precise as you need.
Run history
Every execution recorded with its trigger, the conditions that passed and what each action returned — inspectable and re-runnable.
Dry-run & preview
Test a rule against a real recent event to see exactly what it would do, before a single change is made.
Webhooks
Send an outgoing webhook as an action, or start a rule from an inbound one — a clean bridge to anything InfraNest doesn’t cover natively.
Notification actions
Route a rule to email, Slack, Telegram and the rest, with the message and channel you choose per action.
Audit trail
Every rule change and every run logged with who did what and when, exportable for compliance.
Build your first rule in about two minutes
Start from a recipe, preview it against a real event, then switch it on. Nothing runs until you save.
Doing it by hand vs InfraNest
The difference between remembering to do it and knowing it’s already done.
By hand
- Set up every new domain and server the same way, by hand
- Notice a certificate is expiring only once something breaks
- Get paged during planned maintenance you already knew about
- Steps that live in someone’s head, done a little differently each time
With InfraNest
- Rules onboard new domains and servers automatically
- A trigger acts on an expiry weeks before it bites
- Maintenance windows suppress the planned-work noise
- Every event handled the same, audited way — hands-free
Pairs well with
Frequently asked
Do I need to write any code?
No. The common automations are built from recipes and a guided editor — pick a trigger, add conditions, choose actions. Webhooks and a REST API are there only for the rare case you want to reach a tool InfraNest doesn’t cover yet.
Can a single rule act across different modules?
Yes — that’s the whole point. A trigger from one module, like a domain being registered, can run actions on another, like applying a DNS template and switching on monitoring, all in the order you choose.
What happens if an action fails?
The run is recorded with the failure, and you’re alerted. You decide whether later actions stop or continue, nothing fails silently, and you can re-run the rule once the problem is fixed.
Can I preview a rule before it goes live?
Yes. Dry-run any rule against a real recent event to see exactly what it would do. No changes are made until you save and enable it.
Could an automation do something destructive by accident?
A rule only ever does what its actions say, nothing runs until you enable it, and every run is in the audit trail. Sensitive actions can be held for a confirmation, so nothing risky happens unattended.
Set it once, then forget it
Build a rule from a recipe and let your stack run itself.
Start for free