> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/knowledge-base/setting-up-tillit/activity-templates/activity/when.md).

# When

## **When should this trigger? 3/3**

In this section, you will set the when this activity will trigger.

If left blank, the activity won't trigger with any event, but can be triggered manually. Even when a trigger is assigned, you can still [trigger an activity manually](/tillit/knowledge-base/everyday-usage/activities/manually-starting.md).

### Adding a Trigger

{% stepper %}
{% step %}

### Open the Trigger Menu

Click + Add a trigger to view the available trigger groups.

<figure><img src="/files/i6NmYfg7JMEhDr2HVaIk" alt="Modal showing the &#x27;Add a trigger&#x27; button highlighted under the &#x27;When should this trigger?&#x27; section"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select the Trigger Group

Choose one of the available groups depending on the event source:

<figure><img src="/files/55KKj8oqBXyar8rlrH54" alt="Screen displaying the list of available trigger groups"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select Event Type & Set Values

Under each group will be multiple options. Select the specific event and configure additional parameters such as Interval (how often the activity triggers, e.g., *every 15 minutes*) or Delay (delay after the event occurs, e.g., *30 mins after event*).
{% endstep %}

{% step %}

### Add Additional Rules (Optional)

To add more triggers, click + Add a trigger again.

(To remove a trigger, click the X icon next to it).
{% endstep %}
{% endstepper %}

## Available Trigger Groups & Events

### **Equipment Events**

Equipment status is controlled via Edge using an integration with some from of SCADA (e.g. Inductive Ignition). The events are as follows:

* Equipment blocked
* Equipment completed
* Equipment running
* Equipment starved
* Equipment stopped
* Equipment suspended

<figure><img src="/files/hl9VjgjWLkDfgUQQXP9f" alt="Configuration screen for equipment triggers showing options, alongside input fields for Interval and Delay"><figcaption></figcaption></figure>

When you select an equipment event, you have the option to enter an interval for how often the activity will trigger (e.g. every 15minutes) and/or a delay between the event and when the activity triggers for the first time (e.g. 30mins after the event).

### **Order Events**

Order status can be controlled either in TilliT or via Edge using tags from SCADA. The events are as follows:

* Order canceled
* Order Changeover overrun
* Order Changeover resume
* Order changeover started
* Order completed
* Order created
* Order paused
* Order ready
* Order renewed
* Order resumed
* Order started

<figure><img src="/files/qPuMg7LBNAdSQKirjjvP" alt="Configuration panel for order triggers displaying orders status events, with inputs for Interval and Delay"><figcaption></figcaption></figure>

When you select an order event, you have the option to enter an interval for how often the activity will trigger (e.g. every 15minutes) and/or a delay between the event and when the activity triggers for the first time (e.g. 30mins after the event).

### **Activity Events**

Activity status is controlled in TilliT. The events are as follows:

* Activity expired
* Activity failed
* Activity failed retest
* Activity manually started
* Activity passed
* Activity skipped

<figure><img src="/files/1jrB97dwPbmgZ2T3YhB7" alt="Configuration options for activity triggers showing activity events, with fields for Interval, Delay, and Activity Key selection"><figcaption></figcaption></figure>

When you select an activity event, you have the option to enter an interval for how often the activity will trigger (e.g. every 15minutes) and/or a delay between the event and when the activity triggers for the first time (e.g. 30mins after the event).

<figure><img src="/files/j02MJ31BH1TrOzxpmvyY" alt="Expanded dropdown menu for selecting a specific Activity Key to apply the trigger to"><figcaption></figcaption></figure>

For Activity triggers, you can select the specific activity you want to reference when. For example, you may want to trigger one activity when the Approval to Start - Filler activity passes.

If you don't set an activity key, then the trigger will apply to all activities. For example, you may want to trigger an activity called ***Team Lead Intervention*** when any activity fails a retest.

### **Shift Events**

Shift events happen when shift patterns start and end. The events are as follows:

* Shift ended
* Shift started

<figure><img src="https://s3.amazonaws.com/helpscout.net/docs/assets/60208fd212248b2c96d50eeb/images/6290642a68d51e779444448b/file-KyQrWFb85Z.png" alt="Configuration options for shift triggers showing &#x27;Shift started&#x27; and &#x27;Shift ended&#x27; options, along with Interval and Delay input fields"><figcaption></figcaption></figure>

When you select a shift event, you have the option to enter an interval for how often the activity will trigger (e.g. every 15minutes) and/or a delay between the event and when the activity triggers for the first time (e.g. 30mins after the event).

Shift Templates are set via Asset Hierarchy > Shift Templates.

### **Custom Events**

Custom Events that are created in TilliT will be available here. For more details, see [Event Type](/tillit/knowledge-base/setting-up-tillit/events/event-type.md).

<figure><img src="/files/HiF8sZ1M5EZAGnIptqs6" alt="Dropdown selector for choosing a custom trigger"><figcaption></figcaption></figure>

<figure><img src="/files/YLth07YcGzHgsIQZjsXP" alt="Configuration panel for a custom trigger with &#x27;Weekly Event&#x27; selected, including Interval and Delay input fields"><figcaption></figcaption></figure>

When you select an custom event, you have the option to enter an interval for how often the activity will trigger (e.g. every 15minutes) and/or a delay between the event and when the activity triggers for the first time (e.g. 30mins after the event).
