Workflow Editor Actions Panel
Last updated
Last updated
When editing a user flow, an "Actions" panel or toolbar provides quick access to various components and settings for building and managing your workflow.
This panel typically includes the following options:
Add Trigger:
Icon: Lightning bolt
Description: Allows you to set up or modify the initial condition(s) that will start the workflow. This defines how users enter the flow.
Add Step:
Icon: Stacked items / Drawer (looks like a filing cabinet drawer)
Description: Enables you to introduce a new action or stage within the workflow. Steps are the individual tasks or processes the workflow executes after a trigger.
Use Case: Adding actions like sending an email, updating a user profile, adding a delay, or tracking user events..
Add AB Split:
Icon: Flask / Beaker
Description: Allows you to divide users into different paths within the flow to test variations of a message, timing, or action (A/B testing).
Use Case: Testing two different email subject lines to see which gets a higher open rate, or sending different offers to segments of users.
Entry Criteria:
Icon: Entry arrow
Description: Controls how often users can re-enter this specific workflow. This helps prevent users from being spammed or experiencing the same flow repeatedly in a short period.
Use Case: Setting rules like "a user can only enter this welcome flow once" or "a user can re-enter this cart abandonment flow after 7 days if they abandon another cart."
Exit Criteria:
Icon: Exit arrow
Description: Defines the conditions under which users should be removed from the workflow, even if they haven't completed all the steps.
Use Case: Removing a user from an onboarding flow if they complete a key activation event, or removing them from a promotional flow if they make a purchase.
Note that when you apply an entry / exit criteria through the actions panel it will apply to the whole workflow.
This is a critical distinction as you can also apply entry condition at a step level as well.
To see how this works in practice proceed to the next page on adding steps.
Use Case: Defining if a flow starts based on a user action, a profile update, a schedule, or an API call.