Course Content
Flows – Intermediate
0/5
Configuring an Update Action – AI Agent
00:00
Configuring a Delete Action – AI Agent
00:00
Using Variables – AI Agent
00:00
Conditions – Simple Conditions – AI Agent
00:00
Course Exercise: Creating a Monday account based on Conditional Logic – AI Agent
00:00
Flows – Intermediate

Here is a clear, step-by-step academy guide written to accompany the video. It uses the requested formatting tools to remain highly scannable, structured, and easy for students to follow.

Lesson Guide: Mastering Condition Nodes in Noca Flow

In this lesson, you will learn how to use the Condition Node in Noca Flow to execute conditional logic based on real-time data. We will walk through a real-world example: reading a Salesforce account and automatically categorizing the company size based on its employee count.

Prerequisites

Before starting, ensure you have:

  • An active Noca AI account.

  • A Salesforce integration connected to your Noca workspace.

  • Test accounts in Salesforce (e.g., one with $>100$ employees and one with $<100$ employees).

Step 1: Set Up Your Base Flow and Read Node

First, we need to bring the data we want to evaluate into Noca Flow.

  1. Open your Noca Flow workspace.

  2. Add a Read Node to your canvas to pull an account record from Salesforce.

  3. Configure the Read Node’s condition to look up a specific account name (e.g., Edge Communications).

  4. Set up an Account ID Variable right after the Read Node to store the retrieved Salesforce Account ID for later use.

Step 2: Insert and Configure the Condition Node

The Condition Node will act as a fork in the road, splitting your automation path based on the criteria you define.

  1. Click the + icon on your canvas and select Condition Node.

  2. Look at the configuration panel on the right side of your screen.

  3. Open the Data Kit, navigate to your Read Account Node, go to App Fields, and locate the Number of Employees field (you can use the search bar to find it quickly).

  4. Drag and drop the Number of Employees field into the top portion of the condition statement.

  5. Set the logic operator to Greater than or equal to ($\ge$) and enter 100 as the value.

  6. Name your condition branch more than 100.

💡 What just happened? Your flow has now successfully split into two distinct paths: the top path executes if the account has 100+ employees, while the bottom path (Else) executes if it has fewer.

Step 3: Map the Conditional Actions (Salesforce Update)

Now, we define what happens on each of the two paths.

Path A: More than 100 Employees

  1. Add a Salesforce Update Action node to the more than 100 path.

  2. Select the Account object.

  3. Under mapping, search for the Company Size field and select Large from the dropdown menu.

  4. Set the node’s required condition to match your Account ID variable with the incoming account’s ID so Noca knows exactly which record to update.

Path B: Else (Less than 100 Employees)

  1. Add a second Salesforce Update Action node to the Else path.

  2. Select the Account object.

  3. Under mapping, search for the Company Size field and select Small from the dropdown menu.

  4. Set the exact same variable condition (Account ID $=$ Variable Account ID) so the correct record updates.

Step 4: Save and Test Your Logic

Always test both branches of your conditional logic to ensure the configuration is flawless.

Test 1: Testing the “Large” Path

  1. Update your Read Node to look for Edge Communications (which has 1,000 employees).

  2. Click Save and Run.

  3. Watch the visual execution path: you will see the flow automatically take the top path. Check Salesforce to confirm the Company Size has changed to Large.

Test 2: Testing the “Small” Path

  1. Click Edit Flow and change your Read Node condition to search for Dickinson PLC (which only has 12 employees).

  2. Click Save and Run.

  3. Watch the visual execution path: the flow will now take the bottom Else path. Check Salesforce to confirm the Company Size has changed to Small.

Key Takeaways

  • Data Kit Drag-and-Drop: You can easily drag any field from previous nodes directly into your condition rules.

  • The “Else” Path: Any data that doesn’t meet your primary condition automatically routes down the Else branch, ensuring no data gets left unhandled.

  • Variables Matter: Storing IDs in variables makes it incredibly efficient to map identical conditions across multiple paths.

Previous
Next