---
title: "Triggers"
slug: "triggers"
abstract: "Overview of triggers, the elements that make up a trigger - events, conditions, and actions, and how to create one."
---
# Triggers

> [!note]
> Some calculated property updates caused by task dependencies do not invoke triggers. For more information, see [Event listening](https://doc.sitecore.com/ch/en/developers/cloud-dev/event-listening.html "Event listening").

Triggers automatically execute a set of actions after specific events and under specific conditions. They are evaluated for every *create*, *update*, and *delete* event that occurs in Sitecore Content Hub and are executed asynchronously to prevent delays.

The **Triggers** page provides an overview of the triggers defined and lets you [create new triggers](https://doc.sitecore.com/ch/en/developers/cloud-dev/create-a-trigger.html "Create a trigger"). To access the **Triggers** page, on the Content Hub menu bar, click **Manage** :mdiCogOutline:.

![Triggers page showing an overview of all the Triggers defined.](https://doc.sitecore.com/api/markdown-image/ch/en/developers/cloud-dev/images/manage__triggers.png)

To see general information about a specific trigger, the conditions attached to it, as well as the actions that are taken in response to an event, click a specific trigger to open the trigger details page or click **View details** :mdiInformationOutline:.

A trigger consists of:

- The conditions under which trigger actions are executed as a result of [event listening](https://doc.sitecore.com/ch/en/developers/cloud-dev/event-listening.html "Event listening").
- The [actions](https://doc.sitecore.com/ch/en/developers/cloud-dev/actions.html "Actions") that the trigger executes. Actions specify a set of actions that will be executed in response to an event. An action can represent anything from pushing a message to an Azure service bus to invoking external APIs, pushing a message into an internal Queue, or sending an email to third parties. Actions are stored as entities within Content Hub and users can select from an existing list of actions, modify outdated actions, or create new ones.

> [!note]
> You can create event types for [historical reporting](https://doc.sitecore.com/ch/en/developers/cloud-dev/event-listening.html "Event listening").