> ## Documentation Index
> Fetch the complete documentation index at: https://help.wotnot.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Jump

> Routes the conversation flow to a specific action block.

![Image](https://mintcdn.com/wotnot/9dFb9jDqAX6_tYFX/images/image-310.png?fit=max\&auto=format\&n=9dFb9jDqAX6_tYFX\&q=85\&s=dd5e98c94560e1c3e4fcd4e82af8d053)

Use the **Jump** block to send multiple branches back to a shared step or to create a loop in your flow.

Allows users to jump from one point of the flow to another, without having to create a connection between the blocks.

This becomes extremely helpful when you have a very large chatbot tree, and connecting the two blocks is tough.

# Using the Jump Block

You need to follow the below steps:

1. Drag the **Jump** block onto the canvas.
2. Connect the Jump block to the preceding block in your flow.
3. Select the **Target block** where you want the flow to continue.
4. Save your changes and test the flow.

The target selector lets you choose the block that the flow should jump to.

![Image](https://mintcdn.com/wotnot/YfQKl2QOkXpO0Wk_/images/image-50.png?fit=max\&auto=format\&n=YfQKl2QOkXpO0Wk_\&q=85\&s=26475e7f8f26e462f38b3f3c714cd645)

* Send multiple branches back to the same step.
* Create a loop in your flow.
* Move the flow directly to a specific block without adding additional routing logic.
* Jump to a specific point in another flow when supported.

## Configurations

* **Title**: You can rename the jump block to keep your flow organized and easy to understand
* **Destination**: Select the action block where you want to route the conversation flow to.

Once configured, the conversation will immediately continue from the selected action block when users reach the Jump block.

## Output Path

The Jump block has **no output path**. It terminates its current branch, and control passes directly to the selected target block.

This means you do not need to connect an output port from the Jump block—the selected target block becomes the next step in the flow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.