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

# Triggers

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

The AI add-on contributes the following triggers. The triggers fire on AI agent lifecycle events emitted by Umbraco.AI.Agent.

## AI Agent Run Completed

Alias: `umbracoAI.agentRunCompleted`. Fires when an AI agent run finishes successfully. Use this to react to the agent's response in another automation step.

## AI Agent Run Failed

Alias: `umbracoAI.agentRunFailed`. Fires when an AI agent run fails. Use this to alert an editor or log the failure for review.

## AI Agent Request

Alias: `umbracoAI.agentTrigger`. Fires when an AI agent invokes the automation as a tool. Use this when you want an AI agent to be able to start the automation as part of its workflow.

{% hint style="info" %}
The exact output fields for each AI trigger depend on the agent and the event payload. Inspect a real run in the **Runs** view to see the available fields, then use the binding picker to reference them.
{% endhint %}


---

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