Table of Contents

Jump To block

Desirée M Updated by Desirée M

The Jump To block lets you redirect your flow to another point, either inside the same bot or into a different one. Your design and variables stay intact, making it easy to keep everything consistent.

It’s a helpful solution to simplify your flow by connecting different bots within the same builder.

🤔 What can I use the Jump To block for?

🔗 Within the same bot: Make complex flows simpler by jumping to another block or Brick, which is a reusable piece of your flow.

🔀 To another bot: You can jump to a different bot, either to its starting point or to a specific block, keeping your conversations smooth.

⚙️ How do I set it up?

Jump to a block or Brick in the same bot

Use this when you want to jump to another block or Brick within the same bot. This is especially useful for large bots.

① First, just select the name of the current bot:

② Toggle the "Point to a specific block" option to YES. Then, choose the block or Brick you want to jump to by entering its block ID.

Jump to a different bot

Use this option to jump to another bot. You can jump to the starting point or to a specific block inside it.

The process is the same as above - just select the different bot you want to jump to, toggle “Point to a specific block” to YES and choose the block by its block ID.

🔎 How do I find a block ID?

① Click the three dots to the left of the block (or Brick).

② From the dropdown menu, select Copy block id.

③ The Block ID is now copied - just paste it where needed.

🤖 How can I use Jump to in AI Agents?

When you’re building AI Agents, you’ll also see the Jump to option. This is what your bot does once it finishes its task.

For example, you can connect an AI Agent to a linear bot with a Google Sheets block, so the data collected by the Agent is exported automatically.

You can check out more details here: Jump to in AI Agents

📝 What happens to fields and data when I use the Jump To block?

When you use the Jump To block, the field values travel with the user into the next bot, as long as the fields have the same name. This means you can collect data in one bot and use it seamlessly in another.

Analytics information, however, stays in the original bot. If you want to download or review conversation data, you’ll always need to check the first bot in the flow.

Example: Imagine you have a linear bot (Bot A) that jumps to an AI Agent (Bot B), and then Bot B jumps to a different linear bot (Bot C). Even if each bot collects different information, all values are stored in Bot A but are available to use and reference in all connected bots, as long as the field names match.

Limitations

Please note that any customizations, and all design and layout elements - including custom CSS, JavaScript, backgrounds, and the Persistent Menu - will always come from the first bot where the jump started. Jumping to another bot won’t change how the conversation looks; the design stays from the first bot.
  • This feature isn’t compatible with Flow Analytics, as all fields are stored in the first (main) bot.
  • If you are using a Persistent Menu in the same bot as a Jump To block, please check out this section of the Persistent Menu article to make sure that it will still work properly!

For Landbot (Web)

It works between Web bots and Web AI Agents, you just need to select the bot and the node you are "jumping to".

For WhatsApp

It works between WhatsApp bots and WhatsApp AI Agents, you just need to select the bot and the node you are "jumping to".

For Facebook Messenger

It works between Messenger bots, you just need to select the bot and the node you are "jumping to".

Was this article helpful?

Lead Scoring block

AB Test

Contact