Jump To
The Jump To node redirects workflow execution to any other node on the canvas. Use it to skip sections, create custom loops, or build non-linear execution paths.
Type: JUMP_TO
Color: Purple (#8B5CF6)
Template: END (terminal; no outgoing connections from this node)
Credits: None
Configuration
| Field | Description |
|---|---|
| Target node | Select which node to jump to from the canvas |
The target can be any node, including nodes earlier in the flow (creating a loop) or nodes in a different branch.
How it works
When execution reaches the Jump To node:
- It stops the current execution path
- Resumes execution at the target node
- The target node runs as if it were naturally next in line
When to use
| Pattern | What Jump To does |
|---|---|
| Custom loop | Jump back to an earlier node to create a retry or polling loop |
| Skip section | Jump past a block of nodes you don't need |
| Merge branches | Both If-Else branches jump to the same continuation point |
| Error recovery | On error, jump to a cleanup/notification section |
Example: Custom retry loop
HTTP Request → If-Else (status === 200) →
True: Continue normally
False: Log error → Delay (5s) → Jump To (HTTP Request)
This creates a retry loop: if the API fails, wait 5 seconds and try again.
Infinite loops: If you jump back to an earlier node without an exit condition, you create an infinite loop. Always pair Jump To with an If-Else or counter that eventually breaks the cycle.
For structured loops, use For Each, Repeat, or Loop Until instead of Jump To. Jump To is for edge cases where the built-in loop nodes don't fit your pattern.
Error handling
If this node fails during execution:
- The execution stops at this node (unless Continue on error is enabled)
- The error appears in the Execution History with the full error message
- Downstream nodes don't execute
To handle errors gracefully:
- Enable Continue on error in the node settings
- Add an If-Else node after to check if the operation succeeded
- Route failures to a notification (Send Email, Send Slack)
Debugging
- Check the Execution History for the failed run
- Click the failed node to see its input and error
- Verify the input data is correct (check previous node outputs)
- Test with sample data using the Test tab