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.
Permission Required
You need the Manager role to edit and publish Flows. See Flow 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.
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 all optional. A filter left empty does not restrict the trigger, and tag filters match only when the object has all the selected tags. See Flow Triggers for what each type reacts to.
The interval itself is set on the Hourly, Daily, Weekly, Monthly, or Advanced tab; see Flow Triggers 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 | 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 | 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 | 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. |
| Field | Required | Type | Description |
|---|---|---|---|
| Source Datastores | List | Only operations on the selected source datastores start the Flow. | |
| Source Datastore Tags | List | Only operations on datastores with all the selected tags. | |
| Operation Types | List | Only operations of the selected types (Sync, Profile, Scan). | |
| Operation Status | Option | Only operations finishing with the selected status (Success or Failure). |
| Field | Required | Type | Description |
|---|---|---|---|
| Source Datastores | List | Only tables or files in the selected source datastores start the Flow. | |
| Tables / Files Tags | List | Only tables or files with all the selected tags. | |
| Check Rule Types | List | Only anomalies identified by the selected check rule types. |
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 |
|---|---|---|---|
| Source Datastores | List | Only anomalies from the selected source datastores start the Flow. | |
| Anomaly's Tags | List | Only anomalies with all the selected tags. | |
| Check Rule Types | List | Only anomalies identified by the selected check rule types. | |
| Anomaly Severity (Min) | Number | Only anomalies with a severity equal to or greater than this value. |
| Field | Required | Type | Description |
|---|---|---|---|
| Source Datastores | List | Only anomalies from the selected source datastores start the Flow. | |
| Anomaly's Tags | List | Only anomalies with all the selected tags. | |
| Anomaly Statuses | List | Only changes to the selected statuses. |
The Manual trigger has no additional fields. The Flow only starts when someone runs it; see 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. See Flow Triggers for what each type reacts to.
Step 4: Fill in the fields for the selected type.
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.
One trigger per Flow
To run the same actions from a different trigger as well, clone the Flow and configure the clone's trigger.