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

# Triggers

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

The Workflow add-on contributes the following triggers.

## Workflow Lifecycle Triggers

| Display Name         | Alias                         |
| -------------------- | ----------------------------- |
| Workflow Started     | `umbracoWorkflow.started`     |
| Workflow Completed   | `umbracoWorkflow.completed`   |
| Workflow Approved    | `umbracoWorkflow.approved`    |
| Workflow Rejected    | `umbracoWorkflow.rejected`    |
| Workflow Cancelled   | `umbracoWorkflow.cancelled`   |
| Workflow Resubmitted | `umbracoWorkflow.resubmitted` |

## Task Triggers

| Display Name  | Alias                          |
| ------------- | ------------------------------ |
| Task Assigned | `umbracoWorkflow.taskAssigned` |

## Email Triggers

| Display Name         | Alias                                |
| -------------------- | ------------------------------------ |
| Workflow Email Sent  | `umbracoWorkflow.emailSent`          |
| Reminder Emails Sent | `umbracoWorkflow.reminderEmailsSent` |

## Content Review Triggers

| Display Name             | Alias                                    |
| ------------------------ | ---------------------------------------- |
| Content Review Completed | `umbracoWorkflow.contentReviewCompleted` |

{% hint style="info" %}
Each Workflow trigger emits details about the workflow instance, task, or content review it fired on. Fields include the node ID, entity key, workflow type and status, author, and comment. 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 %}


---

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