---
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


---

# Create record based trigger

# Create a saved record-based trigger {#ariaid-title1}

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

Create a reusable trigger definition that responds to a record-based event. When a record is created or updated in a specific table, the trigger activates and starts the flows where it is used. You can allow flow authors to select the saved trigger, view its conditions, or add their own conditions.

## Before you begin

Role required: trigger_designer, flow_designer, or admin

## Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. On the Workflow Studio home page, select NewTrigger.
3. Fill in the details for your trigger.  
   {#create-saved-trigger__table_l5n_ytp_4dc__entry__2}

   | Field | Description |
   |-|-|
   | Trigger name | Unique name to identify the trigger. |
   | Trigger type | Type of trigger to start your flow. Under Record, select any of the following: * Created: Starts the flow when a record is created in the specified table. * Updated: Starts the flow when a record is updated. * Created or updated: Starts the flow on either event. {#create-saved-trigger__ul_hph_pdl_sfc} For more information about trigger types, see [Workflow Studio flow trigger types](https://servicenow-prod.fluidtopics.net/Soppqn4o7y_LAxzJX99Zpw "Each trigger type defines when a flow starts and the starting data available to it. There are triggers for record operations, dates, and application operations.​"). |
   | Description | Description of the trigger. |
   | Application | Application to create the trigger. The default is Global. The application scope determines which data your trigger can access and what data it can share. |
   [Table 1. New Trigger form]

   {#create-saved-trigger__table_l5n_ytp_4dc}
4. **Optional:** Select Show additional properties and fill any additional properties.  
   {#create-saved-trigger__table_jr1_bnd_5fc__entry__2}

   | Field | Description |
   |-|-|
   | Accessible from | Choice between whether the trigger data should be accessible only from the specified application or all application scopes. |
   | Protection | Option to make the trigger read-only. |
   | Category | Category where your trigger is displayed. |
   | Trigger annotation | Annotation for your trigger that the user can see before they select it. |
   [ ]

   {#create-saved-trigger__table_jr1_bnd_5fc}
5. Select Build trigger.
6. Fill in the trigger definition.  
   {#create-saved-trigger__table_wmd_rw5_4dc__entry__2}

   | Field | Description |
   |-|-|
   | Table | Table for the trigger. The trigger starts when a record is created or updated in the specified table. For example, if you want the trigger to start when an incident is created or updated, select the Incident table. |
   | Conditions | Conditions that, when met, activate the trigger and start the flow. You can select if you want the users to view the conditions or add more conditions to the trigger when they use the trigger in a flow. |
   | Advanced options | Additional options to choose where and when to run the flow. For more information about the advanced options, see [Workflow Studio flow trigger types](https://servicenow-prod.fluidtopics.net/Soppqn4o7y_LAxzJX99Zpw "Each trigger type defines when a flow starts and the starting data available to it. There are triggers for record operations, dates, and application operations.​"). You can select if you want users to view and modify these options when they use the trigger in a flow. If a user modifies the advanced options, any future modifications that you make to these options in the trigger don't affect the user modified settings. |
   [Table 2. Trigger definition form]

   {#create-saved-trigger__table_wmd_rw5_4dc}  
   Tip:  
   Your changes are saved automatically in Workflow Studio.
7. Make the trigger available by selecting Publish.

## Result

The trigger is created and published. You can use the trigger in any of your flows. For information about adding a trigger to a flow, see [Use a saved trigger](https://servicenow-prod.fluidtopics.net/pUsw9zFuv0Fq9pNQC0d4vQ "Instead of creating a trigger, use a saved trigger in your flow. Using a saved trigger enables you to reuse standardized trigger logic across flows, reducing the effort, improving consistency, and simplifying ongoing maintenance.").
**Related concepts**   

* [Saved flow triggers](https://servicenow-prod.fluidtopics.net/txNoM5vvatkS6apnu0rxYg "Save a set of trigger definitions as a reusable trigger. Enable flow authors to select the saved trigger from some or all application flows. Specify whether flow authors can see the trigger details or add conditions to the trigger.")  
**Related tasks**   

* [Create a saved scheduled trigger](https://servicenow-prod.fluidtopics.net/34CBgmHHiwUiPRMFzX0Rlg "Create a scheduled trigger that starts your flow when you need. Schedule the trigger to start your flow on a specific date and time or repeatedly at scheduled intervals. Reuse the trigger in flows that need to run on the same schedule.")
* [Create a saved external trigger](https://servicenow-prod.fluidtopics.net/xoE5~tPAiuAMiuU2ZVsnWg "Save a set of trigger definitions as a reusable trigger that responds to external events through webhooks. When an event occurs in the configured third-party application that meets the specified conditions, the trigger is activated.")

*[\>]: and then