A condition can split a Blueprint into two routes. Use its True output for records that match your rules and its False output for records that do not.
Build two routes
-
Set up the event and condition
Create or open a Blueprint, select its event trigger, then add a condition with the rules that identify the records for your first route. Choose AND if every rule must match or OR if any rule can match.
-
Connect the matching route
Drag a connection from the condition node's True output to an action. For example, when a task priority equals Critical, send a notification to the assigned user.
-
Connect the alternative route
Connect the condition node's False output to a different action if non-matching records need different handling. For example, send a separate notification for other tasks. If no action is connected to that route, the Blueprint does nothing on that branch.
-
Review the connections
Make sure each action is connected to the intended output. An action attached to the trigger rather than a condition branch is not limited to just one of the condition outcomes.
-
Save and test both outcomes
Save the Blueprint and try one record that matches the rules and one that does not. Keep it inactive until you are satisfied with the actions on both routes, then switch it on.
Keep branches easy to read. Give the Blueprint a descriptive name and arrange the True and False actions on separate paths across the canvas.
For more, see Blueprints.