> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/backoffice/automation/trigger.md).
# Trigger
### **Overview**
The **Trigger** feature allows administrators to create and manage triggers that can be used to define automated actions based on a specified time-based expression. Triggers can be added, edited, deleted, and reordered as required.
### **Screen Elements**
| **Screen Element** | **Description** |
| ------------------ | -------------------------------------------------------------- |
| Trigger List | Displays the available triggers. |
| Search | Allows users to search for a specific trigger. |
| Add Trigger | Opens the screen to create a new trigger. |
| Edit Trigger | Allows users to modify the selected trigger. |
| Delete Trigger | Removes the selected trigger after confirmation. |
| Change Sort Order | Allows users to change the order in which triggers are listed. |
| Trigger Name | Field used to enter the name of the trigger. |
| Expression | Defines the time-based condition for the trigger. |
| Common Settings | Provides settings used to configure the trigger expression. |
| Second | Specifies the second value for the expression. |
| Minute | Specifies the minute value for the expression. |
| Hour | Specifies the hour value for the expression. |
| Day | Specifies the day value for the expression. |
| Month | Specifies the month value for the expression. |
| Weekday | Specifies the weekday value for the expression. |
| Save | Saves the trigger configuration. |
| Close | Closes the trigger configuration screen. |
| Test | Tests the configured trigger expression. |
### **Working**
#### **Add a Trigger**
1. Select "Add Trigger" from the Trigger List.
2. Enter the trigger name in "Trigger Name".
3. Configure the "Expression" using the "Common Settings" fields.
4. Specify the required values for "Second", "Minute", "Hour", "Day", "Month", and "Weekday".
5. Select "Test" to test the configured expression, if required.
6. Select "Save" to create the trigger.
#### **Edit a Trigger**
1. Select the required trigger from the Trigger List.
2. Select "Edit Trigger".
3. Modify the required trigger details or expression.
4. Select "Save" to save the changes.
#### **Delete a Trigger**
1. Select the trigger you want to remove.
2. Select "Delete Trigger".
3. Confirm the deletion when prompted.
#### **Change Sort Order**
1. Select "Change Sort Order".
2. Change the order of the triggers as required.
3. Save or confirm the updated order, if prompted.
### **Use Case**
* Schedule automated processes to run at specific times without requiring staff to start them manually.
* Configure recurring actions that need to occur at fixed intervals, such as every minute, hour, day, or week.
* Set different execution times for processes that need to run at specific hours or on specific days.
* Schedule routine operational tasks to run automatically during predefined business hours.
* Configure triggers for processes that need to run on particular days of the month or specific weekdays.
* Support time-dependent automation where an action needs to occur based on a defined date or time pattern.
* Create multiple triggers for different automated processes that require different execution schedules.
* Organize multiple triggers in a preferred order to make them easier to manage when several time-based processes are configured.
### **Notes**
* A Trigger Name is required when creating a trigger.
* Configure the expression using the available time fields.
* Use "Test" to verify the configured expression before saving, if required.
* Deleting a trigger requires confirmation.
* Triggers can be reordered using "Change Sort Order".
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.rbsgo.com/dineplan/backoffice/automation/trigger.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
