> 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/19.latest/add-ons/uibuilder/triggers.md).

# Triggers

Reference for the triggers contributed by the Umbraco.UIBuilder.Automate add-on.

The UI Builder add-on contributes the following triggers.

| Display Name   | Alias                            |
| -------------- | -------------------------------- |
| Entity Saved   | `umbracoUIBuilder.entitySaved`   |
| Entity Created | `umbracoUIBuilder.entityCreated` |
| Entity Deleted | `umbracoUIBuilder.entityDeleted` |

**Entity Saved** fires whenever an entity is created or updated in any registered collection. **Entity Created** fires only the first time an entity is created, not on later updates. Each trigger has an optional **Collection Alias** setting to filter to a single collection; leave it blank to fire for every collection.

{% hint style="info" %}
Trigger output includes the collection alias, the entity ID, and the entity serialized as JSON. Properties configured as encrypted on the collection are omitted from the JSON, so decrypted secrets are never exposed to an automation. Inspect a real run in the **Runs** view to see the exact field names, then use the binding picker to reference them in downstream steps.
{% endhint %}

## Entity Deleted on EF Core

UI Builder 19 uses EF Core by default. With EF Core, **Entity Deleted** behaves differently from earlier versions:

* **Entity Deleted** also fires for soft deletes.
* The entity JSON carries scalar properties only, because EF Core doesn't include navigation properties.

UI Builder sometimes raises a delete for a row that is already gone. **Entity Deleted** skips that delete and doesn't fire.


---

# 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/19.latest/add-ons/uibuilder/triggers.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.
