Advanced node type: Jump with variable passing

Created by Certorix Online, Modified on Mon, 4 May at 9:29 PM by Certorix Online

Jump node with variable passing

When using a Jump node to transfer control to another tree, you can pass variables from the current session to the target tree.

Why pass variables?

Variables allow the target tree to pre‑fill answers or skip steps based on information already collected.

Example: In a 'Customer verification' tree, you collect the customer's name and email. When you jump to the 'Billing support' tree, you pass those values so the customer doesn't have to enter them again.

Configuring variable passing

  1. Click the Jump node to open properties.
  2. Select the target tree.
  3. In the Variable mapping section, click Add mapping.
  4. Select the source variable (from current session). Options:
    • Any answer from a Question node (by node ID)
    • Any value from an Input node
    • sessionId
    • customerEmail (if collected)
    • customerName (if collected)
  5. Enter the target variable name (what the target tree expects). This matches the node ID in the target tree.
  6. Add more mappings as needed.

Example mapping

Source tree (verification):

  • Question node q_name → answer is customer name
  • Input node i_email → value is customer email

Jump node configuration:

  • Source: answers['q_name'] → Target: customerName
  • Source: inputs['i_email'] → Target: email

In the target tree, add a hidden Info node that uses those variables to display a personalized message.

Target tree expectations

The target tree must have nodes with IDs matching the target variable names. If a target variable name does not exist in the target tree, the value is ignored (no error).

Best practice: Document expected variable names in the target tree's description.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article