Actions
Actions define what happens when a user interacts with your experiences or when a condition is met. They are the building blocks that connect user behavior to outcomes in Jimo.
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.
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, when editing a CTA element's Behavior
In the Content Builder, when adding Triggers & Conditions
In Steps Triggers, in the "Then" section of a trigger
In Resource Center Action Blocks, in the Behavior section
In Checklist 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.
For full detailed list of available Actions, see Available Actions.
Automated Actions
Automated Actions are standalone workflows created in the Actions 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
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.
For full details on creating and managing Automated Actions, see Automated Actions.
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:
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 panel of the flow builder.
Applies to: Tours & Modals
For the full list of available actions and their configuration, see Available Actions.
Survey Conditions follow the same If/Then logic as progress triggers, but are specific to Surveys. 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 panel of the survey builder, between each step.
Applies to: Surveys
For the full list of available actions and their configuration, see Available Actions.
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.
Applies to: Tours & Modals, Surveys, Banners, Hints, Checklists, Resource Centers
For the full list of available actions and their configuration, see Available 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 by selecting an Action Block and defining its Behavior.
Applies to: Resource Centers
For the full list of available actions and their configuration, see Available Actions.
Each task in a Checklist 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.
Applies to: Checklists
For the full list of available actions and their configuration, see Available Actions.
Changelog posts 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 by adding a CTA block to your post. You can customize the button text and style, then choose the action.
Applies to: Changelog Posts
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.
Automated Actions can be made available to the Agent as a knowledge source. When enabled, the Agent can trigger these actions during conversations based on user questions.
You configure this in Agent > Knowledge > Actions.
How to Access
Experience Actions
Open any experience in its builder.
Select a CTA element (Primary CTA or Secondary CTA) in the Navigator.
In the properties panel, look for Behavior > Actions.
Click + Add action and choose from the available actions.
Or, for progress triggers:
Open the flow builder for your experience.
Click + Add progress trigger below any step.
Define an "If" condition, then set the "Then" action.
Automated Actions
From the dashboard sidebar, click Actions (marked "Beta").
Click + New Action to create a new automated workflow.
Use the visual workflow builder to design your action.
Best Practices
Choosing the right action
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.
Combining actions effectively
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 instead.
Test your action chains in Preview. Multi-action setups can behave differently depending on timing and page context. Always verify in Preview before publishing.
Progress triggers vs CTA actions
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.
Checklist tasks
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.
Automated Actions
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, the instructions you write determine when the Agent will trigger it. Be specific about the user intent that should activate it.
Last updated