Skip to main content
MindStudio
Pricing
Blog About
My Workspace
Workflow Logic

Jump

The Jump block transfers execution from the current workflow to a specified destination workflow, maintaining the same scope throughout the transition.

Transition execution to another workflow instantly

The Jump block transfers execution from the current workflow to a specified destination workflow, maintaining the same scope throughout the transition. It is configured with a single required parameter — a destination workflow ID — which identifies the target workflow to hand off execution to. There is no output returned by the Jump block itself; its purpose is purely to redirect the flow of execution rather than produce a value.

This block fits into scenarios where a workflow needs to branch into a separate, pre-built workflow without starting a new isolated context. Because scope is preserved across the transition, any variables or state established before the jump remain accessible in the destination workflow. This makes it useful for modular workflow design where common logic is centralized in one workflow and called from multiple others.

Typical use cases include routing users through different processing paths based on earlier conditions, delegating to a specialized sub-workflow after an initial intake step, or chaining together distinct workflow segments that share a common execution context. The Jump block does not return control to the originating workflow after the transition completes.

What you can build

Real-world workflows powered by the Jump block.

Route by User Input

After evaluating a user's initial response, jump to a specialized workflow designed to handle that specific category of request.

Centralize Shared Logic

Multiple workflows jump to a single shared workflow that handles a common task, such as formatting output or logging, avoiding duplication.

Multi-Stage Onboarding

Chain together sequential onboarding steps by jumping from one stage workflow to the next while preserving collected user data in scope.

Conditional Escalation

When a condition block detects a high-priority case, the workflow jumps to a dedicated escalation workflow that applies stricter handling logic.

Modular Content Pipelines

A content processing workflow jumps to a specialized formatting or publishing workflow once the core generation step is complete.

Language or Region Routing

Based on a detected language or region variable, the workflow jumps to the appropriate localized workflow to continue processing.

Ready to add Jump to your workflow?

Get Started Free

Common questions about Jump

What is the required parameter for the Jump block?

The Jump block requires a single parameter: destinationWorkflowId, which is a string identifying the target workflow that execution should transition to.

What does the Jump block return as output?

The Jump block has no output. It does not return a value; its function is solely to redirect execution to another workflow.

Does the Jump block preserve variables and state from the originating workflow?

Yes. The Jump block transitions to the destination workflow while maintaining the same scope, so variables and state set before the jump remain accessible in the destination workflow.

Does execution return to the original workflow after the jump?

No. The Jump block is a one-way transition. Execution continues in the destination workflow and does not return to the originating workflow after the jump completes.

What kinds of workflows commonly use the Jump block?

The Jump block is commonly used in modular workflow designs where logic is split across multiple workflows, in conditional routing scenarios where different paths lead to different workflows, and in multi-stage processes where sequential workflows share a common execution context.

Add Jump to your workflow

Build powerful AI workflows with drag-and-drop blocks. No coding required.