> 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/readme.md).

# Umbraco Automate

Umbraco Automate is an event-driven automation engine built into the Umbraco backoffice. Build workflows with triggers and actions, no external platforms required.

Umbraco Automate brings event-driven automation directly into Umbraco CMS. You build workflows on a visual canvas in the backoffice by combining triggers (events that start a flow) with actions (units of work). No external automation platform is needed.

<figure><img src="https://2417601672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFSbD4KYvchggw3e6MKZh%2Fuploads%2Fgit-blob-ed808808e39f8aa1507136f590dbf6c750a7bf9a%2Fautomation-canvas.png?alt=media" alt="The Umbraco Automate canvas with a trigger and two actions connected."><figcaption><p>An automation built in the visual canvas editor.</p></figcaption></figure>

## Key Features

* **Visual canvas editor** — Build automations by dragging triggers and actions onto a canvas and connecting them.
* **Built-in triggers and actions** — React to content, media, and member events. Make HTTP requests, send email, publish content, and more.
* **Add-on packages** — Install packages such as Slack, Forms, Commerce, Engage, AI, and Deploy to add more triggers and actions.
* **Workspaces** — Group automations and scope which connections and users have access.
* **Connections** — Reusable credential sets for external services such as Slack.
* **Bindings** — Pass data between steps using `${ ... }` syntax with filters.
* **Run history** — Every run is recorded with per-step inputs, outputs, errors, and timing.

## Explore the Documentation

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><strong>Getting Started</strong><br>New to Umbraco Automate? Start here.</td><td></td><td><a href="/umbraco-automate/getting-started/getting-started.md">Overview</a></td><td><a href="https://2417601672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFSbD4KYvchggw3e6MKZh%2Fuploads%2Fgit-blob-9f223d8e30d767f11c116b07c365451407605e09%2FDocumentations%20Icons_Umbraco_Commerce_Get_Started.png?alt=media">Documentations Icons_Umbraco_Commerce_Get_Started.png</a></td></tr><tr><td><strong>Core Concepts</strong><br>Learn how Umbraco Automate is structured.</td><td></td><td><a href="/umbraco-automate/concepts/concepts.md">Core Concepts</a></td><td><a href="https://2417601672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFSbD4KYvchggw3e6MKZh%2Fuploads%2Fgit-blob-ac14214d4af0e11c8b701b6a16ea2239f075458f%2FDocumentations%20Icons_Umbraco_Commerce_Key_Concepts.png?alt=media">Documentations Icons_Umbraco_Commerce_Key_Concepts.png</a></td></tr><tr><td><strong>Using the Backoffice</strong><br>Manage workspaces, build automations, and review runs.</td><td></td><td><a href="/umbraco-automate/backoffice/backoffice.md">Overview</a></td><td><a href="https://2417601672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFSbD4KYvchggw3e6MKZh%2Fuploads%2Fgit-blob-07e0d5c35ebb2091afedbe2deba5bf13d163f565%2FDocumentations%20Icons_Umbraco_CMS_Fundamentals_Backoffice.png?alt=media">Documentations Icons_Umbraco_CMS_Fundamentals_Backoffice.png</a></td></tr><tr><td><strong>Add-ons</strong><br>Install add-on packages to expand the catalogue of triggers and actions.</td><td></td><td><a href="/umbraco-automate/add-ons/add-ons.md">Overview</a></td><td><a href="https://2417601672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFSbD4KYvchggw3e6MKZh%2Fuploads%2Fgit-blob-126a7bb65a139d229fed45b84e5d01a108decf3f%2FDocumentations%20Icons_Umbraco_CMS_Extending_Packages.png?alt=media">Documentations Icons_Umbraco_CMS_Extending_Packages.png</a></td></tr><tr><td><strong>Extending</strong><br>Create custom triggers, actions, and connection types.</td><td></td><td><a href="/umbraco-automate/17.latest/extending/extending.md">Extending</a></td><td><a href="https://2417601672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFSbD4KYvchggw3e6MKZh%2Fuploads%2Fgit-blob-64a50d3ce6c55f39f2376299be446235c2c920db%2FDocumentations%20Icons_Umbraco_CMS_Extending_Backoffice_UI_API.png?alt=media">Documentations Icons_Umbraco_CMS_Extending_Backoffice_UI_API.png</a></td></tr><tr><td><strong>Tutorials</strong><br>Step-by-step guides for editors and developers, from getting started to technical runbooks.</td><td></td><td><a href="/umbraco-automate/tutorials/getting-started-for-editors.md">Tutorials</a></td><td><a href="https://2417601672-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFSbD4KYvchggw3e6MKZh%2Fuploads%2Fgit-blob-35d43482ffd23f75ecaf7d98480e6b64418be390%2FDocumentations%20Icons_Umbraco_CMS_Reference_Configuration.png?alt=media">Documentations Icons_Umbraco_CMS_Reference_Configuration.png</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-automate/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
