> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-automate/18.latest/concepts/automations.md).

# Automations

An automation is a workflow you build in the backoffice. Every automation has:

* Exactly one trigger: the event that starts the workflow.
* Zero or more steps**:** actions and control-flow nodes that run in sequence.
* A draft version and an optional published version.

## Anatomy of an Automation

<figure><img src="/files/fZQPjuzBNgV8Rcfxr9Ya" alt="An automation on the canvas with a trigger, two actions, and an If branch."><figcaption><p>An automation made up of a trigger and several steps.</p></figcaption></figure>

| Part                    | Purpose                                                                          |
| ----------------------- | -------------------------------------------------------------------------------- |
| **Trigger node**        | Subscribes to an event. Outputs data that downstream steps can bind to.          |
| **Action node**         | Performs a unit of work — make an HTTP request, send a message, publish content. |
| **Control flow node**   | Adds branching or looping — If, Switch, While, For Each, Parallel.               |
| **Connections (edges)** | Define the order in which nodes execute.                                         |

## Lifecycle

| Status        | Triggers fire? | Description                                                                                       |
| ------------- | -------------- | ------------------------------------------------------------------------------------------------- |
| **Draft**     | No             | The automation is being edited. It does not respond to events.                                    |
| **Published** | Yes            | The live version runs when its trigger fires.                                                     |
| **Inactive**  | No             | The automation has been explicitly disabled. The published version is retained for re-activation. |

Editing a published automation saves draft changes without disturbing the live version. See [Versioning](/umbraco-automate/18.latest/concepts/versioning.md) for details on rollback.

## See Also

* [Build an Automation](/umbraco-automate/18.latest/backoffice/building-an-automation.md)
* [Triggers](/umbraco-automate/18.latest/concepts/triggers.md)
* [Actions](/umbraco-automate/18.latest/concepts/actions.md)
* [Runs](/umbraco-automate/18.latest/concepts/runs.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-automate/18.latest/concepts/automations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.