Automations can control your cloud servers for you — powering them on, rebooting them, or turning on backups — without you lifting a finger. This is for anyone who wants routine server tasks handled automatically instead of manually.
Overview
- Rules can act on servers in response to events like a monitor going down or a new server being added.
- Every server action is reversible — there is no rebuild, restore or delete option, so a rule can never wipe a server.
- Actions include: Power on server, Reboot server, Shut down server, enabling/disabling backups, and Enable delete protection / Disable delete protection.
NoteServer actions are part of a paid plan. On a free plan they appear in the builder but are greyed out until you upgrade.
Add a server action
- Open Automations, then select New automation (or edit an existing rule).
- Choose a trigger — what should set the rule off (for example a Monitor alert, or Server added).
- Under Do this, choose a server action. These are grouped under Servers.
- Choose which server the action applies to:
- Leave it set to Use the one from the trigger when the trigger already involves a server (like Server added) — the action uses that server automatically.
- Otherwise, use Choose a server… to search and pick a specific server.
- Select Save.
Start from a template
- Go to the Template library (or select Browse all templates).
- Pick one of the ready-made recipes, such as:
- A template that enables backups and protection whenever a new server is added.
- Monitor down → reboot the server — a self-healing rule that reboots the server and notifies the team when a monitor fails.
- Select Use.
- Adjust anything you like — for the reboot recipe, pick which server it applies to.
- Select Save.
TipFor a "reboot when down" rule, keep the built-in cooldown so a flapping monitor can't reboot the server over and over. Add conditions (like a tag) to keep the rule pointed at the right servers.
Tips
- Every server action is written to your Audit Log and shows up in the automation's Run history, so you can always see what ran and when.
Was this article helpful?
Related 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…