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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Create a saved trigger

# Create a saved trigger {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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.

## Before you begin

Role required: trigger_designer, flow_designer, or admin

## Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. From the Workflow Studio home page, select NewTrigger.
3. On the form, fill in the fields.  
   {#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. For more information about trigger types, see [Workflow Studio flow trigger types](https://servicenow-prod.fluidtopics.net/tX0aFIZsckv5T0THcwRybg "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.​"). Note: Starting with the Yokohama release, only record-based triggers are supported for saved flow triggers. |
   | 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. Select Show additional properties.
5. On the form, fill in the fields.  
   {#create-saved-trigger__table_ghd_lwp_4dc__entry__2}

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

   {#create-saved-trigger__table_ghd_lwp_4dc}
6. Select Build trigger.
7. On the form, fill in the fields.  
   {#create-saved-trigger__table_wmd_rw5_4dc__entry__2}

   | Field | Description |
   |-|-|
   | Table | Table for the flow. |
   | 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/tX0aFIZsckv5T0THcwRybg "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 3. Trigger definition form]

   {#create-saved-trigger__table_wmd_rw5_4dc}  
   Tip:  
   Your changes are saved automatically in Workflow Studio. Use the undo and redo buttons as you need.
8. Make the trigger available by selecting Publish.
* **[Create a saved external trigger](https://servicenow-prod.fluidtopics.net/UJmUgBcdXhdHPhedoj22cg)**   
  Save a set of trigger definitions as a reusable trigger that responds to an external event through webhooks. When an event occurs in the configured third-party application that meets the specified conditions, the trigger is activated.

**Related concepts**   

* [Saved flow triggers](https://servicenow-prod.fluidtopics.net/rKHVjQCk4gf8_17O_bXEEA "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.")

*[\>]: and then