Route Workflows with Junctions

Applies to

Bridge by Smartsheet

You can include junctions in Bridge to route your workflow in different directions based on specific criteria.

Junctions have two stages: 

  1. The first is where the decision is made. This is based on input from another system, a user's reply in chat, or data stored from elsewhere in the workflow. 
  2. The second is where the possible options for routing are defined. This can consist of two or more states.

When you create a New Junction, it will initially ask you to name three elements: a junction and two states. You can then drag-and-drop new states below the junction in order to specify additional pathways.

Add a state to a junction

Conditional Junctions

Conditional Junction modules can be used to automatically decide which route to take by applying logic to the answer collected. This answer may be from a question you have asked the user, or it may be from data you have brought in from an external data source during the workflow.

NOTE: refer to the following article for more information on referencing a pre-existing value: Reference Data in the Workflow.

True/False junction modules

All True/False modules will automatically create the junction for you as a group, since there are only two possible pathways for the workflow to follow: success or failure. Once you have added in the preferred type of Conditional Junction, you will need to drag in the states to configure the success and failure branches of the module. 

Example of a True/False junction

You can find these modules by searching for Conditional Junctions or navigating to Utilities > Conditional Junctions. 



Is a referenced value more than another one.


Is a referenced value less than another one.


Does a referenced value equal another one.


Does a referenced string exactly match another one.


Does a referenced string contain another string.

Starts with

Does a referenced string start with another string.

Ends with

Does a referenced string end with another string.

Is Empty

Does the referenced string exist.


As an example, you could determine if someone meets an age requirement by asking for the user’s age. Then, you can compare their answer to the minimum age requirements specified in the More type of Conditional Junction (in this instance, named Age Check).

Age Check Junction


Using external tools to make junction decisions

You can also have external tools interact with Bridge to make junction decisions. 

In this scenario, the workflow is identifying if an account exists in Salesforce or not. If there is an account, it goes down the left path. If there isn't an existing account, it goes down the right path.

Junction using external tools


Conditional junctions with more than two pathways

Multiple routes based on user input

In a chat-based workflow, user input can decide which route a workflow takes. To create multiple options, drag-and-drop additional States below the junction, then specify the criteria for each pathway directly within each State as either a Value or a Context. 

In this example, a user may be asked what product they want to get more information about. Each of the product states (A, B, and C) have contextual data describing the product. Then depending on which product the user mentions, the junction will route the workflow accordingly.

Junction with multiple products based on user choice

There is no limit of how many products could be made available.

Multiple routes based on referenced data

For a non chat-based workflow with more than two pathways, you will first need to add in the Conditional Junction called Junction Match immediately before the Junction itself. This element matches referenced data with its corresponding state (based on the state name) to tell the workflow which path to go down. 

Example of a Junction Match with a Fallback State

For example, if a user has filled out a Smartsheet form identifying Product A, B, or C in a column, you will need to add in the Junction Match element to specify the cell in Smartsheet where the type of product was selected. It will then read the cell and tell the workflow which of the junction state names matches that selected product. 

You will also want to add an alternate state for the workflow to follow if none of the values entered in the cell match either Product A, B, or C. This is called a Fallback State.

Configure the Junction Match 

  1. Open up the Junction Match.
  2. Add the data reference in the Junction field.
    In this example, the data reference is the Product value gathered from the Get Row module. 
  3. Put the name of your alternate state in the Fallback State field. 

Junction Match is case sensitive, so ensure the title of your States are exactly the same as your values. 

Junction Match with example configuration panel open