---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# With a MetricBase trigger

# Create a flow with a MetricBase
trigger {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Start a flow when a MetricBase trigger is met. MetricBase triggers track time series data and can monitor when a threshold is reached, when a trend is detected, or when a system stops reporting data.

## Before you begin

Role required: flow_designer or admin

MetricBase triggers are not
available on the base system. The MetricBase application
requires a separate subscription and must be activated by ServiceNow personnel.

## Procedure

1. Navigate to AllProcess AutomationFlow Designer.
2. Click + NewNew Flow.
3. Define the flow properties.  
   For more information, see [Create a flow in Workflow Studio](https://servicenow-prod.fluidtopics.net/gEVHy7dO3gkmJ7P2I90Ygg "Run a sequence of actions and flow logic when the trigger conditions occur.").
4. In the Trigger section, add a trigger and select MetricBase.
5. Complete the trigger fields.  
   {#create-mb-flow__table_mmj_qtr_fdb__entry__2}

   | Field | Description |
   |-|-|
   | MetricBase Trigger | Select or create a MetricBase trigger record to start the flow. For types of MetricBase triggers, see [MetricBase triggers](https://www.servicenow.com/docs/access?context=metricbase-triggers&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). |
   | Table | Read-only table that contains the metric. |
   | Condition | Click Add filters to set field-based conditions that determine when the flow runs. |
   | Condition Script | Define a script in the Additional MetricBase Trigger Filtering and Moderation table to prevent duplicate metric events from re-triggering a flow. For example, if a metric hovers at a defined trigger threshold, create a script that defines whether to run the flow once when the metric is met, or every time the triggering threshold is exceeded. |
   [ ]

   {#create-mb-flow__table_mmj_qtr_fdb}
6. Add actions, subflows, and flow logic to the flow.
7. Test the flow.
8. Once the flow is behaving as desired, activate the flow.  
   For more information, see [Test a flow](https://servicenow-prod.fluidtopics.net/16GAKmUMqo2akmwgAuG1TA "Before activating a flow so other users can access it, test to make certain it works the way you expect.") and [Activate a flow](https://servicenow-prod.fluidtopics.net/gz_eYvyCFgiOf2838wpXdA "Activate a flow to make it available to run.").

## Result

The MetricBase application monitors time series data on the ServiceNow AI Platform. When the selected trigger is met, the flow runs.

*[\>]: and then