# Configure a Trigger

Source: https://userguide.qualytics.io/flows/flow/how-tos/configure-a-trigger/

Configure the trigger to define when a Flow starts. Every Flow has exactly one trigger node, always present on the canvas; you cannot add or remove it, only change its type and conditions.

> **Note: Permission Required**
>
> To edit and publish a Flow, you need the **Editor** team permission on every datastore it relates to. Admins are exempt. See [Flow Permissions](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/) for details.

## Field reference

The **Trigger Settings** panel starts with the **Start Definition** section, where you pick the trigger type. **Save** stays disabled until a type is selected. Once a type is selected, the other types fold away so its settings have more room, and a trigger you open for editing starts with the list already folded to its saved type. While the list is folded, a **Click to change** hint sits above the selected type. To pick a different type, click the selected one, or press Space or Enter on it, to bring the full list back.

The rest of the panel depends on the selected type. Pick the tab below for your trigger type to see its fields; the filters are optional, except **Datastores** on event triggers, which is required unless you are an Admin or hold the **Editor** team permission on every datastore. A filter left empty does not restrict the trigger. See [Flow Triggers](https://userguide.qualytics.io/flows/flow/deep-dive/triggers/) for what each type reacts to.

### How filters combine

Event triggers group their filters under **Filter Conditions**, with a **Match all** / **Match any** toggle beside the title:

- **Match all** (the default): the Flow starts only when every filter matches.
- **Match any**: the Flow starts when at least one filter matches.

Either way, filters left empty are ignored, except a tags filter set to **is empty** or **is not empty**, which takes no tags and still counts. For example, with **Match any**, **is empty** starts the Flow for an untagged asset even when the other filters don't match. **Datastores** always applies: it is not part of the match, so a Flow filtered on datastores only runs for the datastores it includes, or for every datastore it does not exclude.

### How each filter matches

Each filter has an operator next to its title. Click it to change how the filter compares its values:

| Filter | Operators |
| --- | --- |
| **Tags** filters (**Datastore Tags**, **Tables / Files Tags**, **Anomaly's Tags**) | **is all of** (the default): has every selected tag. **is any of**: has at least one of them. **is not any of**: has none of them. **is empty**: has no tags at all. **is not empty**: has at least one tag. **is empty** and **is not empty** take no tags. |
| **Datastores** | **is any of** (the default): only the selected datastores start the Flow. **is not any of**: every other datastore does, including datastores added later, so saving it needs the **Editor** team permission on every datastore. |
| **Operation Types**, **Check Rule Types**, **Anomaly Statuses** | **is any of** (the default) or **is not any of** the selected values. |
| **Operation Status** | **is** (the default) or **is not** the selected status. |
| **Anomaly Impact** | **is at least** (the default), **is at most**, or **is exactly** the selected level. |

Flows saved before these options existed keep matching as before: **Match all**, with the default operators.

**Tab: Schedule**

The interval itself is set on the **Hourly**, **Daily**, **Weekly**, **Monthly**, or **Advanced** tab; see [Flow Triggers](https://userguide.qualytics.io/flows/flow/deep-dive/triggers/#schedule) for how each interval and cron expressions work. A **Schedule** trigger must have a schedule defined; the Flow cannot be published while the schedule is empty.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Timezone** | No | Option | The timezone the schedule runs in. UTC by default; type to search by city, region, or abbreviation. Applies to every interval tab. |
| **Define a new schedule** | No | Toggle | Shown when the Flow already has a schedule, listed under **Current Schedule** with its timezone abbreviation. Turn it on to replace the schedule. |
| **Custom Cron Schedule** | No | Text | On the **Advanced** tab. A cron expression with five fields, in order: minute (0-59), hour (0-23), day of the month (1-31), month (1-12), and day of the week (0-6, Sunday to Saturday). For example, `0 2 * * *` runs at 2:00 AM every day. Interpreted in the selected timezone (the field label shows its abbreviation). |

| Interval | Description |
| --- | --- |
| **Hourly** | Runs every N hours at a specified minute. For example, **Every 1 hour(s) on minute 0** runs at the top of every hour. |
| **Daily** | Runs every N days at a specific time of day in the selected timezone. |
| **Weekly** | Runs on the selected days of the week at a set time in the selected timezone. |
| **Monthly** | Runs once a month on a specific day at a set time in the selected timezone. |
| **Advanced** | Accepts a **Custom Cron Schedule** for precise control. The cron fields are interpreted in the selected timezone. |

**Tab: Operation Completed**

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Datastores** | Conditional | List | Only operations on the selected datastores start the Flow. Lists only the datastores you hold the **Editor** team permission on. Left empty, the Flow reaches every datastore. |
| **Datastore Tags** | No | List | Only operations on datastores whose tags match, by default those with all the selected tags. |
| **Operation Types** | No | List | Only operations of the selected types, or with **is not any of** of any other type (**Sync**, **Profile**, **Scan**, **Export**, **Materialize**, **Global Export**). A Global Export is matched through the enrichment datastore it writes to. |
| **Operation Status** | No | Option | Only operations finishing with the selected status (**Success** or **Failure**), or with **is not** with the other one. |

**Tab: Anomalous Table or File Detected**

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Datastores** | Conditional | List | Only tables or files in the selected datastores start the Flow. Lists only the datastores you hold the **Editor** team permission on. Left empty, the Flow reaches every datastore. |
| **Tables / Files Tags** | No | List | Only tables or files whose tags match, by default those with all the selected tags. |
| **Check Rule Types** | No | List | Only anomalies identified by the selected check rule types, or with **is not any of** by none of them. |

**Tab: Anomaly Detected**

> **Info: Only open anomalies trigger this Flow**
>
> The **Filter Conditions** section shows this notice. Anomalies recorded as duplicates or resolved by the scan do not trigger the Flow.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Datastores** | Conditional | List | Only anomalies from the selected datastores start the Flow. Lists only the datastores you hold the **Editor** team permission on. Left empty, the Flow reaches every datastore. |
| **Anomaly's Tags** | No | List | Only anomalies whose tags match, by default those with all the selected tags. |
| **Check Rule Types** | No | List | Only anomalies identified by the selected check rule types, or with **is not any of** by none of them. |
| **Anomaly Impact** | No | Option | Only anomalies at the selected level (**Low**, **Medium**, **High**, or **Critical**), compared by the choice next to the field title: **is at least** (the default), **is at most**, or **is exactly**. Left empty, impact is ignored. See [how Impact is decided](https://userguide.qualytics.io/anomalies/deep-dive/triage/impact/). |

**Tab: Anomaly Status Changed**

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Datastores** | Conditional | List | Only anomalies from the selected datastores start the Flow. Lists only the datastores you hold the **Editor** team permission on. Left empty, the Flow reaches every datastore. |
| **Anomaly's Tags** | No | List | Only anomalies whose tags match, by default those with all the selected tags. |
| **Anomaly Statuses** | No | List | Only changes to the selected statuses, or with **is not any of** to any other status. |
| **Anomaly Impact** | No | Option | Only anomalies at the selected level (**Low**, **Medium**, **High**, or **Critical**), compared by the choice next to the field title: **is at least** (the default), **is at most**, or **is exactly**. Left empty, impact is ignored. See [how Impact is decided](https://userguide.qualytics.io/anomalies/deep-dive/triage/impact/). |

**Tab: Manual**

The **Manual** trigger has no additional fields. The Flow only starts when someone runs it; see [Execute a Flow](https://userguide.qualytics.io/flows/flow/how-tos/interactions/execute-a-flow/).

## Steps

**Step 1**: Navigate to the Flows page by clicking **Flows**  on the left side panel.

**Step 2**: On the **Definitions** tab, click the Flow, then click its **Trigger** node. The **Trigger Settings** panel opens on the right-hand side.

**Step 3**: Under **Start Definition**, select the trigger type you want. The other types fold away and the fields for the selected type appear below it. If the trigger already has a type and you want another one, click the selected type, under the **Click to change** hint, to show the full list first. See [Flow Triggers](https://userguide.qualytics.io/flows/flow/deep-dive/triggers/) for what each type reacts to.

**Step 4**: Fill in the fields for the selected type. For event triggers, pick **Match all** or **Match any**, and change a filter's operator next to its title if needed.

**Step 5**: Click **Save**. The trigger node shows the selected type, a **CHANGED** badge appears, and the **You have unpublished changes** banner shows on the canvas. When filters are applied, the node also shows a funnel icon; hover over it to review the conditions.

**Step 6**: Click **Publish**  to make the trigger live.

> **Note: One trigger per Flow**
>
> To run the same actions from a different trigger as well, [clone the Flow](https://userguide.qualytics.io/flows/flow/how-tos/flow/clone-a-flow/) and configure the clone's trigger.

*Last updated: October 28, 2026.*
