Skip to main content

Using Decisions and Branches in Workflows

Configure decision nodes to route workflows to Yes or No branches, and use DecisionSwapYesNo to reverse branch labels.

Written by James Ross

Decision nodes in a workflow present a Yes/No choice that routes the workflow down different branches. This allows conditional logic — different activities execute depending on the decision made.

Decision Routing

  • When the workflow reaches the decision, a prompt appears with Yes and No options.

  • Select the option shown on the main path to continue along the main path.

  • Select the other option to follow the alternate branch.

  • Activities on the unselected branch are marked as Skipped.

  • The progress bar updates to reflect the selected path.

Decision Step Page

When a workflow reaches a decision node, the assignee sees a decision step page below the submission form. This page displays:

  • The decision question configured on the decision node

  • Two choice cards — one for Yes and one for No — each showing the route description for that path

Selecting a Choice

To make a decision:

  • Click the Yes or No card

  • The selected card is highlighted to confirm the selection

  • A route description appears below the cards, explaining which path the workflow will follow

Continue Button

The Continue button is only enabled after a choice (Yes or No) has been selected. If neither option is selected, clicking Continue has no effect — no separate popup appears.

Important: The Continue button does not proceed until a decision is made. This prevents accidental advancement without an explicit choice.

Path Routing

After the decision is made:

  • The workflow follows the selected path (Yes or No) to the next activity

  • Activities on the unselected path are marked as Skipped

  • The run only completes when the chosen path reaches its end — not when the other path ends

This fix ensures that selecting No correctly follows the No path without prematurely completing the run.

Existing workflows with decision nodes continue to work without modification — the Yes path completion and routing logic are backwards compatible.

Related Articles

Did this answer your question?