Product documentation and training for Shipcode.
Basic Operator Nodes: Conditional Logic & Branching
These Nodes create decision points within your Flow, directing execution down different paths based on evaluated conditions or detecting when data has changed.

Conditional

The Conditional Node directs execution to one of two Nodes depending on whether a provided condition evaluates to true or false.


When connecting a Conditional Node:

  • The first Connection you draw will be labeled "true" and should connect to the Node that executes when the condition evaluates to true
  • The second Connection will be labeled "false" and executes when the condition evaluates to false

Troubleshooting Connection Behavior

If your Conditional Node executes the opposite path than expected (the "true" flow runs when the condition is false, or the "false" flow runs when the condition is true), the connections may need to be remapped.


To resolve this:

  • Open the Flow in the Flows editor
  • Delete the existing Connections from the Conditional Node
  • Reconnect the Conditional Node to the correct downstream Nodes, ensuring the first connection goes to the true path and the second connection goes to the false path


This behavior can occur after editing Nodes that follow a Conditional or after reprojecting your application.

Until Changed

The Until Changed Node prevents execution until its input differs from a comparison value you provide in the Key field. This is useful for preventing redundant executions when data hasn't actually changed, such as filtering out duplicate API responses or preventing unnecessary re-renders.


Did this answer your question?