# 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.

Source: https://infranest.io/docs/automation-examples
Last updated: 2026-09-19

---

A collection of ready-to-copy automation ideas to help you get started quickly — useful for anyone who wants inspiration before building their own rules.

## Overview
- Each example below can be built from scratch or used as a starting point.
- They show common combinations of triggers, conditions, and actions.
- You can adjust any of them to fit your own setup.

<!-- screenshot: automation-examples -->

<!-- docs-screenshots:start:automation-examples -->

![Automation examples](/media/5efa834e-bfb4-4762-8ff6-a2bb5e82f62b)

<!-- docs-screenshots:end:automation-examples -->

## Build an example automation
1. Go to **Automations** in the sidebar.
2. Select **New automation**.
3. Choose **Start from scratch**, or select the **Template library** tab to find a similar starting point.
4. Set the **When this happens** trigger to match the example you want to recreate.
5. Use **Add condition** to narrow down when the automation should run, if needed.
6. Use **Add action** to add each step listed in the example.
7. Select **Save automation** when you're done.

## Warn the team about expiring domains
1. Set the trigger to **Domain expiring**.
2. Select **Add condition** and set it so the automation only runs when **Days until expiry** is **less than** 14.
3. Add the **Send notification** action.
4. Add the **Open maintenance window** action.
5. Select **Save automation**.

## Tag and announce a monitor outage
1. Set the trigger to **Monitor alert**.
2. Add the **Add issue labels** action, and enter "incident" under **Labels (comma-separated)**.
3. Add the **Post status-page announcement** action.
4. Select **Save automation**.

## Auto-resolve a recovered incident
1. Set the trigger to **Monitor resumed**.
2. Add the **Resolve incident** action.
3. Select **Save automation**.

## Keep new domains protected
1. Set the trigger to **Domain added**.
2. Add the **Set auto-renew** action.
3. Select **Save automation**.

## Push events to your own tools
1. Set the trigger to **On event** and choose any event you'd like to react to (for example, **Server removed** or **Certificate expiring**).
2. Add the **Call webhook** action.
3. Enter the address of your system under **URL**, and add any details you want to send under **Payload (JSON, optional)**.
4. Select **Save automation**.

## Harden every new server
1. Set the trigger to **Server added**.
2. Add the **Enable delete protection** action.
3. Select **Save automation**.

## Reboot a server when its monitor goes down
1. Set the trigger to **Monitor alert**.
2. Add a condition so **Status** **equals** "down".
3. Add the **Reboot server** action.
4. Add the **Send notification** action.
5. Select **Save automation**.

> [!TIP]
> Add conditions to keep rules focused — for example, only domains with a certain tag, or only certificates flagged as weak.

## Troubleshooting
- If an automation doesn't run as expected, open it from **All automations** and check **Runs** to see its history.
- Use **Test run** to try an automation with sample data before relying on it.
- If a rule keeps failing, look for the **Auto-disabled after repeated failures** notice — you may need to fix a step and turn it back on.