Paths

Paths let you create sequences of conditional steps inside a workflow.

You might think of a Paths as "If X is true, then do A, B & C. Else, do D and E."

Here's a quick video tutorial:

The Basics

Creating a Path group

To create a Path group, navigate to Paths in the Flow Control menu. Next, specify the rules for which Path A should be activated. By default, Path B is set to be activated for cases where no other Path is matching.

Animated demonstration of creating a path group by navigating to Paths in Flow Control menu and configuring conditional rules

Adding Paths to an existing group

To add one or more Paths to a group, click [+].

Animated demonstration of adding additional paths to an existing path group by clicking the plus button

Nesting Paths

It's possible to nest Path groups inside each other, simply by creating a new Path group inside another.

Workflow showing nested path groups with one path group containing another path group inside it

Reordering Paths

Reorder Paths by right-clicking on its header to change the order of evaluation.

Animated demonstration of reordering paths by right-clicking on the path header to access reordering options

Merging paths

In Relay.app it's possible to continue steps on the "common path" after a Path group. Essentially joining or merging the paths. This is helpful if only certain steps need to be conditionally executed.

Data objects of the same type that are created, updated or fetched across all Paths in a group are available as the "output" of the Paths in steps after they join together.

The Step Output of the merged output is indicated with a Path icon instead of a Step number, e.g..

Workflow showing path group merging where Step 5 uses a Contact output that comes from either Step 3 or 4 depending on path taken
The Contact that's used in Step 5 to add a Label to comes out of the Path group above. Which means that it's either the output of Step 3 or Step 4, depending on which Path was taken in a Run.
Animated demonstration showing that merged data objects are only available when every path in a group has compatible step outputs
Merged data objects are only available when *every* Path in a group has a Step that creates, updates, or fetches an object of the same type

Good to know

  • Paths are evaluated from left-to-right, and only one Path within a group will be taken. This means that if the rules of the first Path evaluate to 'true', that Path is taken. Regardless of whether rules of other Paths in the same group match as well

Last updated

Was this helpful?