Building triggers
A trigger contains the start conditions for your automation. You can create separate triggers for each flow or create a reusable saved trigger that you can use in multiple flows.
By creating a saved trigger, you enable the flow authors to use a predefined trigger rather than creating a new trigger definition for their flow. Any changes made to the trigger are propagated to each flow that uses the trigger.
The following video demonstrates how you can use saved triggers in Workflow Studio.
UI elements
The Workflow Studio home page displays a Triggers option in the list of available components and the list of new components.
When you create a new trigger, you must enter the trigger properties on the New Trigger form.
| Field | Description |
|---|---|
| Trigger name | Unique name to identify the trigger. |
| Trigger type | Type of trigger to start your flow. You can create a saved trigger for any of the following trigger types:
For more information about trigger types, see Workflow Studio flow trigger types. |
| 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. |
| Domain | Domain scope of the flow. For more information about domain separation, see Domain separation explained. |
| Accessible from | Specifies if the trigger data is accessible from all application scopes or one application only. |
| Protection | Option to make the trigger read-only. |
| Category | Category under which the trigger will be displayed. |
| Trigger annotation | Annotation for your trigger that the user can see before they select it. |
After you specify the trigger properties and build the trigger, configure and publish the trigger to use in flows.