InfraNestInfraNest
Automation rules

Automation examples

A few ready-to-copy automations to show what's possible. Build any of these under Automations → New automation, or start from the Templates tab.

Works on Free · some options need ProUpdated October 13, 20262 min read

A set of ready-to-copy automation ideas for anyone getting started with InfraNest automations.

#Overview

  • Each example below is a complete automation you can build in a few minutes.
  • Use them as-is, or tweak the trigger, conditions, or actions to fit how you work.
  • Build any of these under Automations → New automation, or start from the Templates tab.
Automation examples

#Warn the team about expiring domains

  1. Go to Automations and select New automation.
  2. Set the trigger to Domain expiring.
  3. Add a condition: Days left less than 14.
  4. Add the action Send notification.
  5. Add the action Open maintenance window.
  6. Select Save automation.

#Tag and announce a monitor outage

  1. Go to Automations and select New automation.
  2. Set the trigger to Monitor alert.
  3. Add the action Set a value to add the tag "incident".
  4. Add the action Post status-page announcement.
  5. Select Save automation.

#Auto-resolve a recovered incident

  1. Go to Automations and select New automation.
  2. Set the trigger to Monitor alert.
  3. Add the action Resolve incident.
  4. Select Save automation.

#Keep new domains protected

  1. Go to Automations and select New automation.
  2. Set the trigger to Domain added.
  3. Add the action Set auto-renew.
  4. Select Save automation.

#Push events to your own tools

  1. Go to Automations and select New automation.
  2. Choose On event and pick All events in a category or a specific event, such as Server removed or Certificate expiring.
  3. Add the action Call webhook.
  4. Fill in the URL and, if needed, the Payload (JSON, optional) and Custom headers.
  5. Select Save automation.

#Harden every new server

  1. Go to Automations and select New automation.
  2. Set the trigger to Server added.
  3. Add the action to enable backups.
  4. Add the action to enable delete protection.
  5. Select Save automation.

#Reboot a server when its monitor goes down Pro

  1. Go to Automations and select New automation.
  2. Set the trigger to Monitor alert.
  3. Add a condition: Monitor status now equals "down".
  4. Add the action Reboot server.
  5. Add the action Send notification.
  6. Select Save automation.

See the Control servers from automations article for the full how-to on building server-reboot automations.

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

Related articles

Try this in your own account

Connect one provider and work through these steps against your own infrastructure.

Free plan · No credit card required · Set up in minutes