🔀 What are Jump Components?
Jump components function as "portals" within your FlowBuilder. They are composed of two fundamental parts that work as a team: the Jump Start (who sends the user) and the Jump Destination (who receives them).
Their use is key to building organized, reusable, and easy-to-maintain flows, avoiding repetition of logic blocks and maintaining fluid conversation without needing to restart it.
📤 1. Jump Start: Redirecting the conversation
The Jump Start is the component responsible for taking the user and moving them to another point.
✅ Typical use case: If a user initiates the flow through option A, but based on their subsequent interaction they should be sent to option B, this component allows you to redirect them directly to the "B" block without cutting the conversation or losing context.
⚙️ Jump Start Configuration
When you select this component, you'll have two main redirection options:
A. Jump to a component (Same flow)
Allows you to define which exact block on your current canvas the conversation will be redirected to.
Select component: From the dropdown, you choose the exact destination where the flow will jump. This step is critical; an incorrect destination can lead the user to messages out of context.
💡 Key tip: Assigning clear names to your destination components (e.g., Main Menu, Validation Error, Payment Declined) greatly facilitates this configuration and prevents logical confusion.
🤓 Create a new jump destination
If you don't yet have the arrival block created on your canvas, you don't need to exit your current configuration.
Enter your Jump Start component.
Press the "Add jump destination" button located in the side panel.
The system will automatically add the new destination component to your flow and you can modify and connect it immediately.
B. Jump to another published flow
This option allows you to redirect the conversation to a completely different flow that is already active. It is extremely useful when:
You work with modular flows (e.g., you have a dedicated Sales flow and a Support flow).
You want to reuse a complete flow without duplicating the work.
📌 Note: You will only be able to select flows that are already in Published status.
🛡️ Repeat Control (Anti-Loops)
To prevent a user from getting trapped in an infinite loop (e.g., failing a validation over and over), the Jump Start includes control tools:
Maximum number of jumps: Define how many times the user can pass through that exact Jump Start. Recommendation: Use low values (3 to 5, only the amount you determine in your tests) to avoid entering a lengthy loop.
Activate Flow End: Define what the system will do when the maximum allowed amount is reached. This ensures a clear exit for the user (e.g., assignment to a human agent) and prevents bot blocks.
📥 2. Jump Destination: Reception and Connection Audit
The Jump Destination is the point of arrival. To make your life easier when building or auditing robust flows, this component includes a Functional Inspector in its side panel.
This tool does not alter the jump logic, but offers two vital capabilities for your visual organization:
✏️ Rename the Destination
You don't have to settle for generic names that make reading your architecture difficult.
On the canvas, double-click a Jump Destination component to open its side panel.
Locate the name at the top and click the edit control (pencil icon).
Type the new name and save. The label will update immediately on the canvas.
💡 Note: This change is completely safe. Renaming a destination does not break the connections or the logic of the jumps that already pointed to it.
🔎 Track Connected Starts (Origins)
If you're editing a complex flow and wondering "Where are users coming from to reach this point?", the inspector gives you the answer immediately.
With the Jump Destination panel open, go to the "Connected Jump Starts" section.
You'll see a detailed list with the name of each Jump Start component whose output reaches this destination.
Click the arrow icon next to any item in the list and the canvas will automatically scroll to center you on the exact location of that origin.
⚠️ Jump Destination Considerations
Orphan Destination Management: If you audit a flow and clicking on a Jump Destination shows you the message "No Connected Jump Starts", it means that destination is no longer in use. It's an excellent signal to clean up unnecessary nodes on your canvas.
Exclusive Scope: This inspector panel applies only to the Jump Destination component. It does not modify the settings of the Jump Starts, which remain intact in their own panel.
✅ Checklist before publishing
Before activating your interconnected flows, make sure to review:
Organization: Are the destination components named clearly and descriptively?
Accuracy: Does each Jump Start point to the correct block?
Logic: Do the chosen destinations make sense within the user's experience and context?
Testing: Did you test all possible paths (and jump limits) in the simulator?
Your flows are now perfectly connected! 🚀
By mastering the Jump Start and Jump Destination components, you avoid repetitive configurations and keep your bot's architecture flawless. Use the inspector to audit your dependencies with just a couple of clicks and take your automation to the next level. ✅