Lesson Guide: Advanced Condition Nodes & Multi-Rule Logic

In this lesson, we will upgrade our conditional routing by evaluation multiple variables simultaneously. You will learn how to use AND operators to chain logic rules together, create multiple execution branches within a single Condition Node, and handle default fallback scenarios using the Else path.

Logic Strategy Overview

We are classifying Salesforce accounts into three distinct options using two fields: Number of Employees and Number of Locations.

Step 1: Add a Second Segment (AND Logic) to Rule 1

Instead of checking just one requirement, let’s configure our first rule to check two.

1. Open your existing Noca Flow from the previous lesson.

2. Click on your Condition Node to open the properties panel on the right.

3. Select your first rule (formerly more than 100).

4. Click Add Segment to create a second criteria block inside this same rule.

5. Set the Join Operator to AND (meaning both conditions must evaluate to true to pass).

6. Open your Data Kit, find the Number of Locations field from your Read Node, and drag it into the top section of your new segment.

7. Change the operator to Greater than ($>$) and set the value to 1.

8. Update the associated Salesforce Update Node to map Company Size to Large Multilocation.

Step 2: Create a Second Rule Branch

A single Condition Node can manage multiple custom rules before hitting the final “Else” statement. Let’s add our second track.

1. In the Condition Node panel, click Add Rule.

2. Name this new rule branch less than 100.

3. Configure the first segment of this rule: drag Number of Employees, set the operator to Less than ($<$), and enter 100.

4. Click Add Segment and ensure the Join Operator is set to AND.

5. Drag Number of Locations into this segment, set the operator to Greater than ($>$), and enter 1.

Step 3: Rewire the Canvas Connections

Now we need to visually map our new logic rule to its corresponding actions.

1. Disconnect the old link feeding into your second update node.

2. Click and drag a new connection line directly from your newly created less than 100 rule output over to your second Update Node.

3. Open this Update Node and change the Company Size mapping value to Small Multilocation.

Step 4: Configure the Fallback (Else) Path

The Else path captures any scenario that doesn’t perfectly fit into Rule 1 or Rule 2 (e.g., companies that only have 1 single location).

1. Add a brand new Salesforce Update Action node onto the canvas.

2. Link the remaining Else output pin of your Condition Node directly to this new node.

3. Inside the configuration panel, choose the Account object.

4. Set the mapping for Company Size to Single Location.

5. Set the required record validation condition: Account ID $=$ your Project Variable Account ID.

Step 5: Save and Test Your Multi-Branch Automation

Test 1: Testing the Single Location (Else) Path

1. Open your Read Node, and set the lookup condition to Dickinson PLC (12 employees, 1 location).

2. Click Save and Run.

3. Result: Because it fails both rules (having only 1 location), you will see the flow take the bottom Else path. Check Salesforce to confirm it now reads Single Location.

Test 2: Testing the Large Multilocation Path

1. Click Edit Flow and change your Read Node condition to search for Edge Communications (1,000 employees, multiple locations).

2. Click Save and Run.

3. Result: The data validates both segments of Rule 1, sending the execution down the top path. Check Salesforce to confirm it successfully updates to Large Multilocation.

Key Takeaways

• Join Operators: Use AND when all segments in a rule must be met; use OR if satisfying any single segment is enough.

• Multi-Branch Routing: You can stack multiple distinct rules inside a single Condition Node to cleanly split your business logic into 3, 4, or more distinct operational paths.

Ready to take your flows a step further? Join us in the next lesson where we will dive into using the Switch Node for handling complex structural shifts!