Linking inputs in decision tree nodes

Release version: Australia

Updated March 12, 2026

2 minutes to read

Summarize

Summarized using AI

Summary of Linking Inputs in Decision Tree Nodes

Linking inputs in decision tree nodes allows authors to reuse input values from previous nodes, streamlining the decision-making process for agents. This functionality reduces redundancy by automatically filling in answers based on prior inputs, thereby enhancing efficiency during runtime.

Show full answer Show less

Key Features

Linking Inputs in Question Nodes: When an input is linked to another, the associated question is not displayed to the agent, as the value is automatically populated. For instance, if a credit card number is collected in the start node, it can be reused in subsequent questions without requiring the agent to answer again.
Linking Inputs in Guidance Nodes: Inputs can also be linked to guidance inputs, allowing the reuse of customer-provided answers. For example, linking a task input from the start node can provide necessary information for actions such as case reassignment.
Special Cases for Linking: While inputs can typically only be linked to prior inputs of the same type, the application supports specific cases such as linking string inputs to various field types, reference inputs with matching input tables, and choice inputs with string types.

Key Outcomes

By utilizing input linking, ServiceNow customers can streamline their decision trees, minimize the need for repetitive input from agents, and ensure that relevant information flows seamlessly through the process. This capability not only improves agent efficiency but also enhances the overall user experience during case handling.

Linking of inputs enables decision tree authors to reuse input values (answers) from prior nodes.

Linking inputs in question and linking nodes

Most questions are presented to an agent to provide answers. When you link an input to another input, the question is not displayed to the agent. Because the input reuses values from the input it is linked to, the agent does not need to provide any answer.

Similar to other inputs, you can use linked inputs to create path conditions.

Question related to credit card number in a decision node that reuses the answer from the start node. — Figure 1. Example of linking inputs in a question node

For example, if you have already asked the credit card number in the start node, you can reuse that input in the following question node. This question is not presented to the agent again and the value is automatically filled out during run time.

Linking inputs in guidance nodes

With linking inputs, you can reuse the answers that customer provided to supply input values to the guidance inputs. You can link the task input in the start node to the guidance inputs to pass the information about the record that the agent is working on.

The reassign case guidance uses the input mapping feature to link the task input in the start node to the guidance input. — Figure 2. Example of linking inputs in a guidance node

For example, you can connect the start node’s task input to the following guidance. The task input holds a reference of the record the agent is working on in a workspace. You need a case number, which is provided by the task input, for reassigning the case to someone else.

Special cases for linking inputs

In most cases, you can only link inputs to other prior node’s inputs of the same type. For example, you can link a string input field type to another string input field type.

The Guided Decisions Experience application supports the following special cases.

Table 1. Cases supported in the Guided Decisions
Input type	Description
String input field type	Accepts any type of field to be linked. For example, string accepts integer, decimal, choice, and others. String is a text field which accepts any characters.
Reference input field type	Accepts only reference type of field. You can link reference input types only if the current question node’s input table matches the prior node’s input table at the same level or at the child level. For example, the Task table can be linked to the Task table or the Task table can be linked to the Case table, which is a child of the Task table.
Choice input field type	Accepts choice type and string type because a choice in a choice list is a string.
Date and Date/Time input field types	Accepts the following types: `glide_date_time` `glide_date` `date` `datetime` `due_date` `calendar`

Note:

The Guided Decisions Experience application does not support glide_var type fields to map to any inputs.