# Actions

### What are Actions?

In Jimo, an **Action** is any operation that gets executed in response to a user interaction or a triggered condition. Actions are the "then" part of every interaction: a user clicks a button, *then* something happens. A condition is met, *then* something happens.

Actions appear in two distinct contexts in Jimo:

* **Experience Actions** : Actions assigned to CTA buttons and progress triggers inside your experiences (Tours, Surveys, Banners, Hints, Checklists, Resource Centers). These are configured in the experience builder and execute when end-users interact with your in-app content.
* **Automated Actions** : Standalone no-code workflows that run independently from experiences. These are created and managed from the dedicated [**Actions**](https://i.usejimo.com/actions/no-code) section in the dashboard sidebar. They can be triggered by the [Agent](https://help.usejimo.com/docs/experiences/agent) or run as part of automation flows as any other experience action.

This page covers the concept of Actions across Jimo. For detailed setup of each action type, see the sub-pages below.

***

### Experience Actions vs Automated Actions

Understanding the difference between these two types is key to using Jimo effectively.

#### Experience Actions

Experience Actions are the actions you assign to **CTA buttons** (Primary CTA, Secondary CTA) and **progress triggers** within any experience. They define what happens when a user clicks a button or when a trigger condition is met.

**Where you configure them:**

* In the [Flow Builder](https://help.usejimo.com/docs/builders/flow-builder#flow-visualization-and-step-progression), when editing a CTA element's Behavior
* In the [Content Builder](https://help.usejimo.com/docs/builders/content-builder#advanced-customization-options), when adding Triggers & Conditions
* In [Steps Triggers](https://help.usejimo.com/docs/triggers-and-conditions/steps-triggers#then-trigger), in the "Then" section of a trigger
* In [Resource Center](https://help.usejimo.com/docs/experiences/resource-center/components#action-block) Action Blocks, in the Behavior section
* In [Checklist](https://help.usejimo.com/docs/experiences/checklists/behavior#main-task-action) Tasks main action, in the Behavior section

**Example:** A user clicks "Learn more" (Primary CTA) in a Tour step, and the action **Launch Experience** starts another Tour. Or a progress trigger detects a button click, and the action **Navigate to** sends the user to a specific page.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FtciRoHxz5pnEqOtrL3WF%2Fimage.png?alt=media&#x26;token=faae7b6b-6284-4658-8c88-e36be5bfc970" alt=""><figcaption></figcaption></figure>

For full detailed list of available Actions, see [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions).

***

#### Automated Actions

Automated Actions are standalone workflows created in the [**Actions**](https://i.usejimo.com/actions/no-code) section of the dashboard. They don't live inside an experience. Instead, they are independent no-code automations that can be triggered by the Agent or composed into sequences.

**Where you configure them:**

* In the dashboard sidebar, go to [**Actions** > **No-code**](https://i.usejimo.com/actions/no-code)

**Example:** An Automated Action called "Navigate to Admin Settings" that the Agent can trigger when a user asks "Where are the admin settings?" during a conversation.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FC6LyOCZKE3cgq517X7WT%2Fimage.png?alt=media&#x26;token=ed8e34f0-d694-46f8-89f8-2986d79fbc55" alt=""><figcaption></figcaption></figure>

For full details on creating and managing Automated Actions, see [Automated Actions](https://help.usejimo.com/docs/build/actions/automated-actions-no-code).

***

### Where Actions are used

Actions appear across Jimo in several places. Here's a summary of where you'll encounter them and how they connect:

{% tabs %}
{% tab title="Progress Triggers" %}
Progress triggers let you define **If/Then** logic on each step of a flow. The "Then" part is an action. When the "If" condition is met (e.g. a user clicks a specific element, fills an input, or a based on a specific survey answer), the action executes.

You configure trigger actions in the [Progress Triggers](https://help.usejimo.com/docs/build/triggers-and-conditions/steps-triggers) panel of the flow builder.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FVbvOmqjxNNagOatsBcs9%2Fimage.png?alt=media&#x26;token=4a155328-ff83-43e3-94b2-87efb7a02d19" alt=""><figcaption></figcaption></figure>

**Applies to:** [Tours & Modals](https://i.usejimo.com/tours)

For the full list of available actions and their configuration, see [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions).
{% endtab %}

{% tab title="Survey Conditions" %}
Survey Conditions follow the same If/Then logic as progress triggers, but are specific to [Surveys](https://help.usejimo.com/docs/experiences/surveys/flow-builder). The "If" part is based on **user answers** to survey questions (e.g. "If the user selects option A" or "If NPS score is below 7"), and the "Then" part is an action.

By default, there's a fallback "Then" action type **Go to step**.

You configure conditions in the [Conditions](https://help.usejimo.com/docs/build/triggers-and-conditions/conditions) panel of the survey builder, between each step.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FUc3xlbtV6kPD8kzTvtIV%2Fimage.png?alt=media&#x26;token=932e62e3-ac5e-465f-a448-45afe049a1ed" alt=""><figcaption></figcaption></figure>

**Applies to:** [Surveys](https://i.usejimo.com/surveys)

For the full list of available actions and their configuration, see [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions).
{% endtab %}

{% tab title="CTA Buttons" %}
Most experience type in Jimo supports CTA buttons (Primary CTA, Secondary CTA, Checklist Task, RC Action). When a user clicks a CTA, the assigned action executes.

You configure CTA actions in the experience builder by selecting a CTA element and choosing an action from the **Behavior > Actions** dropdown.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FLLx71CFW9lpqdK9pE9Ml%2Fimage.png?alt=media&#x26;token=e2cf3ded-43ef-418f-845c-1bffd26d2471" alt=""><figcaption></figcaption></figure>

**Applies to:** [Tours & Modals](https://i.usejimo.com/tours), [Surveys](https://i.usejimo.com/surveys), [Banners](https://i.usejimo.com/banners), [Hints](https://i.usejimo.com/hints), [Checklists](https://i.usejimo.com/checklists), [Resource Centers](https://i.usejimo.com/resource-centers)

For the full list of available actions and their configuration, see [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions).
{% endtab %}

{% tab title="Resource Center Actions" %}
Resource Center Action Blocks are clickable cards that execute actions when a user clicks them. They work differently from CTAs: instead of a button inside a step, the entire block is the clickable area.

You configure them in the [Resource Center Builder](https://help.usejimo.com/docs/experiences/resource-center/components#action-block) by selecting an Action Block and defining its Behavior.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F5W6BCJ5ncdvWzEfiiG9M%2Fimage.png?alt=media&#x26;token=9f7318d6-2343-4b7b-8041-ade5f4a5d322" alt=""><figcaption></figcaption></figure>

**Applies to:** [Resource Centers](https://i.usejimo.com/resource-centers)

For the full list of available actions and their configuration, see [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions).
{% endtab %}

{% tab title="Checklist Tasks" %}
Each task in a [Checklist](https://help.usejimo.com/docs/experiences/checklists/behavior#main-task-action) is itself an action. When a user clicks on a task, the assigned action executes. This is how checklists drive users through onboarding steps, feature discovery, or setup flows: each task represents one action to complete.

You configure task actions in the Checklist builder by selecting a task and defining its action in the Behavior section.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FDtkEbQ09OIBQH8SI7gNj%2Fimage.png?alt=media&#x26;token=19567a37-17a9-42ea-adfb-9b529f63223c" alt=""><figcaption></figcaption></figure>

**Applies to:** [Checklists](https://i.usejimo.com/checklists)

For the full list of available actions and their configuration, see [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions).
{% endtab %}

{% tab title="Changelog Posts CTA" %}
[Changelog posts](https://help.usejimo.com/docs/experiences/changelog/posts/post-components) support a single CTA button with a simplified interface compared to other experiences. The available actions are limited to **Launch Experience** (start a Tour, Survey, or other experience) and **Navigate to URL** (redirect to a page).

You configure the CTA in the [Post Builder](https://help.usejimo.com/docs/experiences/changelog/posts/post-builder) by adding a CTA block to your post. You can customize the button text and style, then choose the action.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F9SG4YD9G7JiR3dGS4dzi%2Fimage.png?alt=media&#x26;token=9f87609c-aa93-4f59-b6e9-63b2c2bbfe21" alt=""><figcaption></figcaption></figure>

**Applies to:** [Changelog Posts](https://i.usejimo.com/feed)

> **Note:** Changelog Post CTAs do not support the full range of actions available elsewhere (no Launch Agent, Dismiss, Go to Step, Run JS, etc.). This is by design, as posts are standalone announcements rather than multi-step flows. For details, see [Post Components](https://help.usejimo.com/docs/experiences/changelog/posts/post-components#call-to-action-cta-button-f).
> {% endtab %}

{% tab title="Agent Knowledge" %}
Automated Actions can be made available to the [Agent](https://help.usejimo.com/docs/experiences/agent) as a knowledge source. When enabled, the Agent can trigger these actions during conversations based on user questions.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F0C487iBfXySEGLmq8wQX%2Fimage.png?alt=media&#x26;token=dc46020e-33cb-4f33-bd63-43247f7d78b5" alt=""><figcaption></figcaption></figure>

You configure this in [Agent > Knowledge > Actions](https://i.usejimo.com/agent/knowledge/actions).
{% endtab %}
{% endtabs %}

***

### How to Access

#### Experience Actions

1. Open any experience in its builder.
2. Select a **CTA element** (Primary CTA or Secondary CTA) in the Navigator.
3. In the properties panel, look for **Behavior > Actions**.
4. Click **+ Add action** and choose from the [available actions](https://help.usejimo.com/docs/build/actions/available-actions).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FggAIF7hNWi1RCku94FRC%2Fimage.png?alt=media&#x26;token=841b515a-99a7-4ca4-a345-0c695e2ca925" alt=""><figcaption></figcaption></figure>

Or, for progress triggers:

1. Open the flow builder for your experience.
2. Click **+ Add progress trigger** below any step.
3. Define an "If" condition, then set the "Then" action.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FXYdxg7UEEX7Mazcc5koZ%2Fimage.png?alt=media&#x26;token=2d044d41-1996-4ca5-ab72-a5dd599f468b" alt=""><figcaption></figcaption></figure>

#### Automated Actions

1. From the dashboard sidebar, click **Actions** (marked "Beta").
2. Click **+ New Action** to create a new automated workflow.
3. Use the visual workflow builder to design your action.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FNT1BxNUPZMpX4Hlo5Ka6%2Fimage.png?alt=media&#x26;token=c003b827-dbf1-40ad-a8c2-2ce395947dc0" alt=""><figcaption></figcaption></figure>

***

### Best Practices

<details>

<summary><strong>Choosing the right action</strong></summary>

* **One action per CTA, one goal per click.** If a user clicks "Learn more", the expected outcome should be clear. Avoid stacking unrelated actions on the same button.
* **Use Navigate to for simple redirects, Launch Experience for guided flows.** If the user just needs to land on a page, Navigate to is enough. If they need hand-holding once they get there, chain a Launch Experience instead.
* **Reserve Launch Agent for open-ended or complex questions.** The Agent shines when users need conversational help. For straightforward tasks, a direct action (Navigate to, Launch Experience) is faster and more predictable.

</details>

<details>

<summary><strong>Combining actions effectively</strong></summary>

* **Put tracking before navigation.** If you combine Run JavaScript Code with Navigate to or Launch Experience, place the JS action first. Navigation changes what the user sees, so any tracking or data push should happen before.
* **Limit stacked actions to 2-3 max.** More than that and the user experience becomes unpredictable. If you need complex sequences, consider using an [Automated Action](https://help.usejimo.com/docs/build/actions/automated-actions-no-code) instead.
* **Test your action chains in Preview.** Multi-action setups can behave differently depending on timing and page context. Always verify in [Preview](https://help.usejimo.com/docs/build/preview) before publishing.

</details>

<details>

<summary><strong>Progress triggers vs CTA actions</strong></summary>

* **Use CTA actions for explicit user choices.** The user deliberately clicks a button. They expect something to happen.
* **Use progress triggers for implicit behavior.** The user fills an input, clicks a native element, or scrolls to a section. The trigger detects it and reacts automatically, without requiring the user to click a Jimo button.
* **Combine both for smart flows.** A CTA can advance to the next step, while a progress trigger on that step auto-detects when the user completes the real task and moves them forward.

</details>

<details>

<summary><strong>Checklist tasks</strong></summary>

* **Each task should map to one clear action.** "Set up your profile" should Navigate to the profile page or Launch a Tour that guides the user through it. Don't leave tasks without an action, as users won't know what to do.
* **Use Launch Experience to combine Checklists with Tours.** This is the most effective onboarding pattern: the Checklist provides the structure, and each task launches a Tour that provides the guidance.

</details>

<details>

<summary><strong>Automated Actions</strong></summary>

* **Start with low-risk actions.** Navigation and page-opening actions are safe starting points. Save data-modifying automations for when you're confident in the trigger logic.
* **Write clear instructions when connecting to the Agent.** If you make an Automated Action available to the [Agent](https://help.usejimo.com/docs/experiences/agent), the instructions you write determine when the Agent will trigger it. Be specific about the user intent that should activate it.

</details>