# Steps Triggers

## Overview

The **Steps Triggers** feature lets you define specific events that trigger actions within a step. You can set multiple triggers per step, each with its own conditions (If) and actions (Then). This enables you to create highly interactive and responsive user experiences.

### **Accessing the Triggers Tab**

* Navigate to the desired step in the tour builder.
* Click on the **Triggers** tab in the side panel.

<figure><img src="/files/fT4fW0em0qCBdMn2awH5" alt=""><figcaption></figcaption></figure>

### **Adding Triggers**

* Click **Add Trigger** to create a new trigger.

<figure><img src="/files/ZqNypcJSkBrUWHxljr6F" alt="" width="406"><figcaption></figcaption></figure>

* Define the "If" condition and the "Then" action for the trigger.

<figure><img src="/files/kS3qNoVP4ummoNdBPC57" alt="" width="362"><figcaption></figcaption></figure>

#### Examples

<figure><img src="/files/NVW0PUZRDKGYguTjRSeM" alt="" width="403"><figcaption></figcaption></figure>

1. **Button Click Navigation**
   * **If:** Button A is clicked
   * **Then:** Navigate to Step 2
2. **Input Filled Action**
   * **If:** Input field is filled
   * **Then:** Dismiss experience

## If Trigger

The "If" trigger sets the condition that must be met for an action to occur. It allows you to specify criteria based on user interactions or other events that will trigger the subsequent action.

<figure><img src="/files/mW7HHDG0ciI8QFL5j0QR" alt=""><figcaption></figcaption></figure>

### Setting Conditions (If)

Conditions define the criteria for triggering an action. This logic is similar to [events](/docs/analyze/success-tracker/events.md) in success trackers and the "[on event trigger](/docs/publish/trigger-on-the-right-spot-show-on.md#on-event)" in experience settings. Use conditions to create specific, event-based workflows within your tours. Conditions can be combined using AND/OR logic.

<figure><img src="/files/KYlLC9o5yZi3lqYrAL8F" alt=""><figcaption></figcaption></figure>

### Types of Conditions (If)

* **Element**: Triggers when an element is present, clicked, or hovered. Ideal for interactive elements like buttons or links.

<figure><img src="/files/5TUKGo9CweNhaynP2zBG" alt=""><figcaption></figcaption></figure>

* **Fills in Input**: Triggers when a specific input field is filled. Useful for form completions.

<figure><img src="/files/RDoSyVoaqEucxIQGRm9s" alt=""><figcaption></figcaption></figure>

* **Current Page URL**: Triggers based on the current page URL. Perfect for page-specific actions.

<figure><img src="/files/fescQCbZn2h20AbdDOf0" alt=""><figcaption></figcaption></figure>

* **Delay**: Triggers after a specified delay. Useful for timed actions.

<figure><img src="/files/4g8utYpGZusWX4cLSdrG" alt=""><figcaption></figcaption></figure>

## Then Trigger

The "Then" trigger defines the action that occurs once the "If" condition is met. It specifies what happens next in your workflow, ensuring a smooth and logical progression.

<figure><img src="/files/GuPR3amgGvQONZSAh6qn" alt=""><figcaption></figcaption></figure>

### Defining Actions (Then)

Actions are the responses triggered by the conditions. Similar logic can be found in previous [CTA actions](/docs/experiences/tours-and-modals/components.md#cta-actions) but with enhanced capabilities. Actions can be combined by adding multiple actions.

<figure><img src="/files/ahB5BRiFOzWx8tmdUyGu" alt=""><figcaption></figcaption></figure>

### Types of Actions (Then)

* **Go to Step**: Navigate to another step within the tour. Useful for creating multi-step processes.

<figure><img src="/files/43ROcNSJYD4N5HyTT9FG" alt=""><figcaption></figcaption></figure>

* **Dismiss Flow**: Ends the current experience. Ideal for concluding a tour or modal.

<figure><img src="/files/5zFxEgrvdhLW3QyQXnNn" alt=""><figcaption></figcaption></figure>

* **Launch Experience**: Starts another Jimo experience. Useful for chaining experiences. (Works only with published experiences, you can't launch drafts.)

<figure><img src="/files/qrRCjIlFMRdLQ4ha6aSD" alt=""><figcaption></figcaption></figure>

* **Navigate to**: Sends the user to a specific page URL, either absolute or relative. Perfect for directing users to different parts of your site.

<figure><img src="/files/Mq3Nkn8vIqvJyWYBOmUy" alt=""><figcaption></figcaption></figure>

* **Run JavaScript Code**: Executes custom JavaScript code. Ideal for advanced custom actions and integrations.

<figure><img src="/files/uQKIyC9qtwsDJFJsFGYJ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://help.usejimo.com/docs/build/triggers-and-conditions/steps-triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.