Introduction
Recently, the option to loop in automation has been added. This enables you to create automations that route contacts back to earlier points in the flow, effectively “teleporting” them from one node to another.
Use Cases
Potential Use Cases consist of:
After navigating down a branch, users can be brought back to a main menu to explore other options.
Form Correction: If a user realizes they’ve taken the wrong path in a form, they can jump back and revise inputs.
Looping Input Collection: Repeat a specific sequence (e.g., requesting an image or file) multiple times based on conditions.
How It Works
Node Placement: You can insert a “Jump to” node almost anywhere in your automation, provided certain logical and technical constraints are respected.
Origin & Destination: Each Jump to Node is configured with:
An origin — the point in the automation that triggers the jump.
A destination — the node where the contact is redirected.
Flow Logic: Once a contact reaches the origin node, they are instantly rerouted to the destination node, skipping over intermediary steps.
Think of it as a teleporter: A contact enters at one point in the flow and exits at another, earlier point, enabling smarter branching logic and revisitation of decision points.
You can check whether the connection has been established successfully by checking the destination node.
Limitations & Constraints
To maintain system integrity and avoid logical inconsistencies, Jump to Node comes with the following restrictions:
Jump Restrictions:
Cannot jump forward in the flow — only back to earlier nodes.
Cannot be placed directly after:
A trigger
A “wait for reply” node
A contact deletion node
Loop Prevention:
Each Jump to Node is capped at 20 executions per automation run to avoid infinite loops or spam.
Node Interoperability:
Jump to Node cannot target:
Triggers as destinations or origins
“Wait for reply” nodes as destinations
Its direct predecessor node
Error Handling:
If the destination node is deleted, the Jump to Node loses its mapping and blocks publishing until resolved.
Duplication of destination nodes does not replicate mappings. The new node must be manually re-linked.
Exchange ideas with experts from your industry in our community. This is the best place to gather initial ideas, especially at the beginning:
Join our Superchat Community