Automation rules
When something happens, run the actions you choose — hands-free.
Articles
About automationsAutomations let InfraNest react to things happening across your infrastructure on its own.Automation conditionsConditions decide when a rule actually runs. Without them, a rule runs on every matching event; with them, it runs only when the event's details match.Automation examplesA few ready-to-copy automations to show what's possible. Build any of these under Automations → New automation, or start from the Templates tab.Placeholders and formattingPlaceholders let an automation drop live details from the event into a message, title or webhook — so instead of a generic "A certificate is expiring" you…Check your automation runsOnce a rule is live, InfraNest records every time it runs — so you can confirm it's working and see exactly what each action did.Start from an automation templateTemplates are ready-made automations you can adopt in a couple of clicks — the fastest way to see what automations can do without designing one from scratch.Automation triggers and actionsThe full list of what an automation can react to (triggers), the ways to narrow when it runs (conditions), and what it can do (actions).Control servers from automationsAutomations can act on your cloud servers — so a rule can power a server on, reboot it, or turn on backups without you lifting a finger.Create an automationSet up a rule that runs actions automatically whenever a matching event happens. A rule reads as When → If → Then: when an event fires, if your conditions…