Available Actions
A complete reference of every action available in Jimo, where each one can be used, how to configure it, and which actions can be combined.
Overview
When you add an action to a CTA button, a progress trigger, or a survey condition, you choose from the list below. Some actions are available everywhere, others are specific to certain contexts.
Jimo has 9 actions in total. Eight are selectable from the action dropdown, and one (Book Interview) is a fixed action that appears automatically on a specific step type.
Action Types List
Launch Agent
Opens the Agent AI chat, optionally with a pre-filled message. The Agent responds based on your knowledge base, and can suggest Tours or trigger Automated Actions.
Available in: CTA buttons, Progress triggers, Survey Conditions
Configuration
Message (optional): A pre-filled question or prompt that the Agent will immediately process when it opens. Supports plain text.
Attributes (optional): Click "Add attribute" to insert dynamic user data into the message (Jimo Email, Jimo Username, or any custom attribute). Attributes are inserted as chips and resolved at runtime.
Use cases
At the end of an onboarding tour, offer "Have more questions? Ask our AI assistant."
As a CTA in a hint about a complex feature, pre-fill a question like "Explain pricing tiers."
From a progress trigger, detect when a user lands on a settings page and open the Agent with a contextual prompt.
For full details on the Agent, see the Agent documentation.
Go to Step
Navigates to a specific step within the current experience. This enables non-linear flows where users can skip ahead, go back, or branch to different steps based on their actions or answers.
Available in: CTA buttons, Progress triggers, Survey Conditions (default action)
Configuration
Choose step: Select the target step from a dropdown. Options include:
Next step: Advances to the next step in the flow (default behavior).
Previous step: Go back to the last visited step in the flow (only on CTAs).
Complete tour: Marks the experience as completed and closes it.
Specific steps: Jump to any other step in the experience, listed by name and step number.
Use cases
Create branching logic: if a user clicks "I already know this", skip to step 5.
Add a "Go back" button that returns to the previous step.
In a survey condition: if NPS score is 9-10, jump to a "Thank you" step. If 0-6, jump to a "Tell us more" open question.
In Survey Conditions, you have a fixed Go to step action as default fallback behavior.
Every condition between survey steps starts with "Go to step: Next step" fallback which you can change to any other step.
Dismiss Experience
Closes the current experience immediately. The experience is marked as dismissed for the user, which affects recurrence rules and segmentation.
Available in: CTA buttons, Progress triggers, Survey Conditions, Closing cross (default)
Configuration
No additional configuration needed. The action simply closes the experience.
Triggered by the closing cross: The closing cross (X button) on Tours, Banners, and Surveys triggers a Dismiss by default. This means users who close an experience via the cross are tracked the same way as users who click a "Dismiss" CTA.
Use cases
Add a "Skip" or "Not now" secondary CTA that lets users explicitly dismiss.
In a progress trigger: if a user clicks the page's native close button (detected via CSS selector) or navigates out of the flow (detected via the URL), dismiss the Jimo experience to avoid it getting stuck.
Dismissing (and completion) is tracked and can be used for segmentation.
You can create segments based on "Has dismissed" to exclude users who already closed an experience, or to show a follow-up experience later.
Launch Experience
Starts another Jimo experience directly from the current one. This lets you chain experiences together for multi-step workflows. It will automatically dismiss the previous flow.
Available in: CTA buttons, Progress triggers, Survey Conditions, Changelog Post CTA, Resource Center Action Blocks, Checklist Tasks
Configuration
Start experience: Select the experience to launch from a searchable dropdown. Experiences are grouped by type (Tours, Surveys, Checklists, etc.).
Only published (live) experiences are listed.
To make an experience only accessible via actions and SDK use a "No automatic trigger" in the "Show on" settings.
Use cases
Chain a feature tour at the end of an onboarding checklist step.
From a Banner announcing a new feature, launch a Tour that walks users through it.
From a Resource Center action block, let users start a guided setup flow.
In a Changelog Post CTA, invite users to try the new feature via a hands-on Tour.
The launched experience respects its own targeting and display rules.
If the user doesn't match the experience's audience or page conditions, it won't appear.
Open Post
Opens a specific Changelog post directly. Useful for linking users to product updates, release notes, or announcements.
Available in: CTA buttons, Progress triggers, Resource Center Action Blocks, Checklist Tasks
Use cases
In a tooltip about a feature, link to the changelog post explaining the latest improvements.
In an Agent Custom Answer, attach an "Open Post" action to share release notes.
In a Resource Center, surface recent product updates as action blocks.
Navigate to
Redirects the user to a specific URL or page within your application.
Available in: CTA buttons, Progress triggers, Survey Conditions, Changelog Post CTA, Resource Center Action Blocks, Checklist Tasks
Configuration
URL: The destination URL. Can be an absolute URL (e.g.
https://yourapp.com/settings), a relative path (e.g./settings/billing), or an external URL. The URL field also supports dynamic attributes: click the attribute icon to insert user-specific variables (Jimo Email, Jimo Username, custom attributes) that are resolved at runtime.
Open in: Choose where the page opens:
Same tab: Replaces the current page.
New tab: Opens in a separate browser tab.
Use cases
After an onboarding step, direct users to the relevant settings page.
In a Resource Center, link to external documentation or a booking page.
Build a personalized URL with the user's ID:
/users/{custom_attribute}/profile.
Snooze Experience
Temporarily hides the experience and shows it again later. Unlike Dismiss which closes permanently (for the current recurrence cycle), Snooze lets the experience come back after a defined delay. The view is still tracked in the stats but it doesn't apply to the recurrence settings.
Available in: CTA buttons (1st step only), Progress triggers (1st step only), Survey Conditions (1st step only), Closing cross (1st step only)
Configuration
Snooze for: How long to hide the experience before showing it again. Set a number and unit (Hour).
Up to: Maximum number of times the experience can be snoozed.
After this limit (Up to 5 maximum), the next display will not offer the snooze option, it will act as a dismiss.
Triggered by the closing cross: On the first step of a Tour, Banner, or Survey, the closing cross (X button) can be configured to trigger a Snooze instead of a Dismiss. This gives users a "not now" option without permanently dismissing the experience.
Use cases
Show an NPS survey that users can snooze for 24 hours if they're busy, up to 3 times.
A feature announcement banner that comes back the next day if snoozed.
Allow users to delay an onboarding tour without losing it entirely.
Important: Snooze is only available on the first step of a sequential flow (Tour, Banner, or Survey).
Run JavaScript Code
Executes custom JavaScript code when the action triggers. This is the most flexible action, enabling any custom behavior you can code.
Available in: CTA buttons, Progress triggers, Survey Conditions, Resource Center Action Blocks
Use cases
Track a custom event in your analytics tool (e.g. push to Amplitude, Mixpanel).
Push a custom attribute to Jimo for segmentation (e.g. mark a feature as "discovered").
Trigger a third-party widget or integration.
Implement a "dismiss forever" behavior by pushing a custom event, then using it in segment conditions.
This action requires activation by Jimo support.
Contact your CSM or support team to enable it for your project. In the action dropdown, it appears greyed out with the mention "Contact our support to enable this feature." You'll just have to sign an agreement.
Book Interview
Opens a scheduling widget (Calendly, Google Calendar, or Zcal) directly from the experience.
Available in: Primary CTA of a Book Interview survey step type (fixed, cannot be added or removed)
Configuration
The Book Interview action is preset and fixed on the Primary CTA of a "Book Interview" survey step type. You don't select it from the action dropdown.
Instead, you choose the Book Interview step type when building your survey, and the CTA action is automatically configured.
Provider: Configured at the step level (Calendly, Google Calendar, Zcal).
Link: The scheduling link URL, also configured at the step level.
For setup details on scheduling integrations, see Calendly, Google Calendar, Zcal.
Use cases
At the end of an NPS survey: "Would you like to tell us more? Book a 15-min call."
In an onboarding flow: "Need help getting started? Schedule a session with our team."
Availability by Context
Not all actions are available in every context. Here's the full reference:
Launch Agent
Yes
Yes
Yes
No
No
No
No
-
Go to step
Yes
Yes
Yes (default)
No
No
No
No
No
Dismiss
Yes
Yes
Yes
Yes (default)
No
No
No
No
Launch experience
Yes
Yes
Yes
No
Yes
Yes
Yes
via Tours or Custom Answers
Open Post
Yes
Yes
No
No
No
Yes
Yes
via Custom Answers
Navigate to
Yes
Yes
Yes
No
Yes
Yes
Yes
via Automated Actions or Custom Answers
Snooze
1st step
1st step
1st step
1st step
No
No
No
No
Run JS code
Yes*
Yes*
Yes*
No
No
Yes
No
No
Book Interview
Fixed**
No
No
No
No
No
No
No
*Disabled by default. (Requires support activation based on a signed security agreement.)**Fixed action on Book Interview survey step type (Primary CTA only). Cannot be added or removed manually.
Combining Actions
You can assign multiple actions to a single CTA button or progress trigger. Not all actions are compatible with each other.
Combination Matrix
The table reads: "When the row action is already added, these column actions can still be combined with it."
Launch Agent
-
Yes
No
No
No
Yes
Yes
Yes
No
Go to step
No
-
No
No
No
Yes
Yes
Yes
No
Dismiss
No
Yes
-
No
No
Yes
Yes
No
No
Launch exp.
No
Yes
No
-
No
Yes
Yes
Yes
No
Open Post
No
Yes
No
No
-
Yes
Yes
Yes
No
Navigate to
Yes
Yes
Yes
Yes
Yes
-
Yes
Yes
No
Run JS
Yes
Yes
Yes
Yes
Yes
Yes
-
Yes
No
Snooze
Yes
Yes
No
Yes
Yes
Yes
Yes
-
No
Book Interview
No
Yes
No
No
No
No
Yes
No
-
Reading this table: Find the first action you added in the leftmost column. Then look across the row to see which other actions can be combined with it. For example, if your first action is "Launch experience", you can add Go to step, Navigate to, Run JS, or Snooze as a second action.
Execution order
When multiple actions are assigned, they all execute simultaneously. There is no await mechanism between actions, meaning all actions fire at the same time rather than waiting for each to complete.
The nominal execution order is:
Go to step
Launch experience
Dismiss
Book Interview
Open Post
Run JavaScript code
Navigate to
In practice, since there is no await between them, the order mainly matters when one action has a visual side effect that could interfere with another (e.g. Navigate to changes the page, which could interrupt a Launch experience on the same page).
Keep combinations simple and predictable.
The safest pattern is to combine a data/tracking action (Run JS) with a navigation/UI action (Go to step, Navigate to, Launch experience). Avoid combining two actions that both change what the user sees.
Last updated