Automation examples

Ready-to-copy automation recipes for InfraNest, written for anyone who wants to save time without building an automation from a blank page.

Overview

• Each example below is a real automation you can recreate in a few minutes.
• Build any of them from Automations → New automation, or open the Templates tab and look for a similar starting point.
• Use them as-is, or adjust the trigger, conditions, and actions to fit how your team works.

Warn the team about expiring domains

1. Create a New automation and choose Domain expiring as the trigger (When this happens).
2. Under Add condition, set Days until expiry less than 14.
3. Add the Send notification action to alert your team.
4. Add a second action, Open maintenance window, so the renewal work is tracked.
5. Save automation.

Tag and announce a monitor outage

1. Create a New automation with the Monitor alert trigger.
2. Add the Add issue labels action — or if you're tagging the monitor itself, use the tagging action for monitors — and add a label such as "incident."
3. Add the Post status-page announcement action so subscribers are notified automatically.
4. Save automation.

Auto-resolve a recovered incident

1. Create a New automation with the Monitor resumed trigger (a monitor comes back up).
2. Add the Resolve incident action.
3. Save automation.

Keep new domains protected

1. Create a New automation with the Domain added trigger.
2. Add the Set auto-renew action and turn it On.
3. Save automation.

Push events to your own tools

1. Create a New automation and pick any trigger you want to react to — for example Server removed or Certificate expiring.
2. Add the Call webhook action.
3. Fill in the URL your system should receive the event at, and optionally a Payload (JSON, optional) and Custom headers.
4. Save automation.

Harden every new server

1. Create a New automation with the Server added trigger.
2. Add the Enable delete protection action.
3. Add a second action to enable backups.
4. Save automation.

Reboot a server when its monitor goes down

1. Create a New automation with the Monitor alert trigger.
2. Add a condition: Status equals "down."
3. Add the Reboot server action.
4. Add the Send notification action so your team knows a reboot happened.
5. Save automation.

NoteThis one has more moving parts than the others. See Control servers from automations for the full walkthrough.

Tips

TipAdd conditions to keep rules focused — for example, only domains with a certain tag, or only certificates flagged as weak.