> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atollhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automations

> Create, test, enable, and safely defer trigger-based automation rules.

Automation rules run actions when an event matches their trigger and optional conditions. Open **Settings → Automations** to create and manage rules.

You must be an organization owner or admin to access automation settings.

## Create your first rule

Choose **Guide me through my first rule** when no rules exist, or **Guided setup** from the rules page.

<Steps>
  <Step title="Choose a trigger">
    Name the rule and select the event that should start it.
  </Step>

  <Step title="Add conditions">
    Narrow which matching events qualify. You can continue without conditions when every event should qualify.
  </Step>

  <Step title="Add actions">
    Choose at least one action for Atoll to perform when the rule matches.
  </Step>

  <Step title="Review and create">
    Review the trigger, conditions, and actions. Guided setup always creates the rule **disabled**, so saving it cannot start live automation.
  </Step>

  <Step title="Run a dry run">
    Test the exact newly created rule. A dry run evaluates the rule without enabling it. If you edit the rule afterward, run a new dry run because the earlier result no longer applies.
  </Step>

  <Step title="Enable explicitly">
    Select **Enable rule** only after a successful dry run. The rule remains disabled if enabling fails, and you can retry from the same rule card.
  </Step>
</Steps>

<Warning>
  **Finish later** ends the guided continuation but leaves the saved rule disabled. It does not publish or enable the automation.
</Warning>

## Recover from an interrupted setup

* If Atoll returns a definite creation error, correct the error and retry.
* If the create request loses its response or Atoll cannot read a successful response, do not resubmit it. The rule may already exist; reload the page and inspect the rules list before creating another rule. This avoids duplicates.
* If the new rule card cannot be found after refresh, reload the page. No rule is enabled automatically.
* If a dry run fails or returns an invalid result, retry it. Enablement stays unavailable until the exact current rule has a successful result.
* If enablement fails, the rule remains disabled.

You can also choose **New rule** for the standard builder. That path preserves the existing rule behavior and does not add the guided disabled-create and dry-run continuation.