Flow designerAbout nodes

Configure jump nodes

Jump Node

The Jump To Node is your “go-to” shortcut for sending the flow directly to any other Step or Branch node in the graph—skipping everything in between. In programming terms, think of it like a goto statement: as soon as the Jump To Node executes, the engine immediately pivots to the specified target node, regardless of where you are. Use this sparingly, but it can be incredibly powerful for handling loops, centralized error paths, or rerouting after dynamic decisions.

1. Purpose & Behavior

  • Immediate Re-Routing: The moment the Jump To Node runs, it abandons any remaining outgoing nodes from the current node and transports the flow straight into the designated target.

  • No AI Output: Like a Branch Node, a Jump To Node does not generate any text or ask questions. Its sole purpose is to redirect the execution pointer.

  • Circumvent Linear Flow: Instead of drawing multiple arrows or duplicating the same logic in two places, you can have “common” steps (e.g., error handling, “ask for clarification,” “go back to start”) and simply jump there.

2. Jump To Node Fields & Configuration

  1. Label (Optional)

    • What It Is: You can give your Jump To Node a human‐readable label (e.g., “Goto ErrorHandler” or “Loop Back”). It helps both humans and AI to understand the node goal better.

    • Recommendation: Even though it’s optional, name it after the target node—e.g., “Jump to ValidateEmail” instead of leaving it blank.

  2. Branch or Step (Dropdown)

    • What It Is: A dropdown that lists every Branch Node and Step Node in your flow. Choose exactly one destination.

    • How to Use:

      1. Click the “Branch or Step” field.

      2. Scroll or type to filter and pick the node you want to jump to.

      3. Once selected, the Jump To Node will show the target’s name beneath its icon (e.g., “→ ValidateEmail Step”).

    • Key Rule: You cannot jump to another Jump To Node. Only Steps or Branches are valid targets.

3. When Does the Jump Occur?

  1. Immediate Execution

    • As soon as the preceding node (Step, Conversation, or Branch) finishes, if its outgoing node leads into a Jump To Node, the flow does not pause, ask the user, or run any AI instructions: it simply “teleports” to the chosen target node.

  1. No Waiting for User Input or Actions

    • The Jump To Node never waits for user text or for any API action. It’s effectively zero‐time—no “thinking” or “speaking.”

4. Common Use Cases

  1. Centralized Error Handling

    • Instead of duplicating nodes in multiple places, put that prompt into a single Step Node called “Error Handler,” and in every place you want to recover from an error, drop in a Jump To that points to “Error Handler.”

  2. Skipping Over Steps

    • Suppose you have steps A → B → C → D. Under certain conditions (e.g., user is an admin), you want to skip B and C and jump straight to D. Instead of waiting inside a Branch Node to route around B/C, you can have B’s “admin” node lead into a Jump To that points to D.

  3. Reusing Common Subroutines

    • If you have a “Collect Billing Info” subflow that appears from multiple points in your conversation, put that whole subflow under a labelled Step Node (“Collect Billing Info Start”). From any other node, drop in a Jump To pointing there. Once “Collect Billing Info” finishes, have its final node lead back to where you want to resume.

5. Best Practices & Tips

  1. Avoid “Spaghetti” by Labeling Clearly

    • Pitfall: If you cascade Jump To nodes without labels or documentation, the flow becomes impossible to visualize. You’ll click a Jump and get lost.

    • Solution: Give every Jump To Node a descriptive label (e.g., “Jump to Offer Upsell,” “GoTo EndFlow”), and name the target Step/Branch nodes clearly.

  2. Don’t Overuse Jumps for Simple Branching

    • Pitfall: Using Jump To in place of a Branch Node to route to two different places based on a condition is overkill. If you’re simply splitting once, use a Branch Node. Jump To is best for explicit rerouting or loops.

  3. Use Jump To to Maintain a Single Source of Truth

    • If two distinct branches eventually converge back into the same sequence of steps, use Jump To to target that later sequence. That way, if you need to change “ShippingOptions,” you only edit that one node instead of updating separate copies.

6. Best Practices Checklist Before Hitting “Save”

  1. Label Every Jump To Node: “Jump to [TargetName]” rather than leaving it “Jump to” or blank.

  2. Confirm No Self-Referencing Loops: Check that you aren’t jumping directly or indirectly back to the same Jump To node.

  3. Pair with Branch for Controlled Rerouting: If a Jump To is conditional, always insert it after a Branch Node so you know exactly why you’re jumping.

7. When Not to Use a Jump To Node

  • Simple Linear Progression: If you just want to go from Step A → Step B in sequence, don’t clutter the graph with a Jump To in between. Connect A’s outgoing arrow directly to B.

  • Basic Branching Logic: If your goal is merely “if X then do this, else do that,” a Branch Node is clearer. Jump To is overkill for two‐way splits.

8. Summary & Key Takeaways

  1. Jump To = Immediate Redirect: As soon as execution reaches this node, the flow pointer teleports to the chosen Step or Branch—no waiting, no intermediate logic, no AI output.

  2. Use It for Loops, Error Paths, and Shared Subflows: Centralize repeated logic into one place and Jump there whenever needed.

  3. Combine Wisely with Branch and Step Nodes: Branch Nodes decide if you should reroute; Jump To Nodes decide where to reroute.