> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/configurator/rules/triggers.md). # Triggers Overview Browse every trigger type available in the configurator, with use cases and inclusion logic explained. {% hint style="info" %} New to rules? Read [Rules Overview](/configurator/rules/overview.md) first to understand how triggers and actions work together. {% endhint %} ## Main trigger types The configurator supports six trigger types. Each one defines the condition that fires a rule. | Trigger type | Description | Example use case | | ----------------- | -------------------------------------------------- | --------------------------------------------------------------------------- | | **Always Active** | Fires continuously, regardless of user interaction | Apply zoom on every option change | | **Event** | Fires on a specific configurator event | See [Event-based trigger subtypes](#event-based-trigger-subtypes) below | | **Filter** | Fires based on filter attribute conditions | Trigger when the fabric type filter is set to *Wool* | | **Option sets** | Fires when a specific option set value is selected | When *Leather* is selected, prevent *Extra thick foam* | | **Options** | Fires when a specific individual option changes | When size is *1800mm*, auto-select *Heavy duty* metal thickness | | **Whole block** | Fires when any value in an entire block changes | Behaves like Option sets but applies across all sets and options in a block | ## Event-based trigger subtypes When using the **Event** trigger type, select one of the following events: | Event | Description | Example use case | | --------------------------- | --------------------------------------------- | ------------------------------------------------------------------------------------------ | | **Click Button Widget** | User clicks a button widget | Click **Next** to open the next group; click **Reset** to clear a group's selections | | **Click Hotspot** | User clicks a 3D hotspot | Move to a specific camera position or play an animation | | **Click Mesh Group** | User clicks a mesh group in the 3D view | Click a leg mesh to open the leg options panel; click a drawer front to animate it opening | | **Close Hotspot** | User closes the 3D information panel | Return the camera to its default position | | **Configurator loaded** | The configurator finishes loading | Open a specific option group in the side panel on load | | **Event triggered** | A system or custom event fires | Listen for predefined events (such as *Add to Cart* or *Show Summary*) or custom events | | **Group open** | An option group is opened | Set a camera angle to zoom in on the element being customised | | **Group close** | An option group is closed | Reset the camera to its default angle | | **Quantity change** | Any quantity value changes | — | | **Quantity decreased** | A quantity value is decreased | — | | **Quantity increased** | A quantity value is increased | — | | **Widget open** | A widget is opened | Set a custom camera position when the Colour Picker or Print on Demand widget opens | | **Widget closed** | A widget is closed | Reset the camera position | | **Click Dimensions button** | User clicks the dimensions icon on the canvas | Switch to a specific camera view when dimensions are shown | ## Trigger inclusion types For Option sets, Options, Filter, and Whole block triggers, an inclusion type controls exactly when the trigger fires: | Inclusion type | When it fires | | ----------------- | ------------------------------------------------------------------ | | **Is one of** | The selected value matches one in your specified list | | **Is not one of** | The selected value is anything except those in your specified list | **Example:** Set the trigger to *Leg finishes* with inclusion type *Is not one of* and value *Black*. The rule fires whenever the customer selects any leg finish except Black. ## OR and AND conditions ### OR conditions Select multiple values within the same trigger to create OR logic. The rule fires if any of the values match. **Example:** Trigger when *Leg Finish = Metal* OR *Leg Finish = Wood*. ### AND conditions Add multiple triggers to the same rule to create AND logic. All conditions must be met simultaneously. **Example:** Trigger when *Leg Finish = Metal* AND *Seat Shape = Round*. ### Limitations * OR and AND conditions cannot be nested. * You can combine multiple OR and AND conditions on a single rule to build precise trigger logic. ## Combining triggers with actions Different actions are compatible with different trigger types. See [Actions Overview](/configurator/rules/actions.md) for the full list. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.mimeeq.com/configurator/rules/triggers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.