Flows – Advanced

Course Exercise: Looping through Salesforce Accounts and Creating them in Monday.com

In this hands-on workshop exercise, you will learn how to scale your automation pipelines from handling a single, isolated record to processing a bulk collection of multiple data objects seamlessly.

When managing enterprise systems, data rarely arrives one record at a time. To handle mass data sets efficiently, your flows need to capture complete lists and process each row sequentially. In this lab, you will learn how to rewrite an integration query to fetch a bulk collection of data and configure a looping engine to prepare your flow for iterative, high-volume data syncing.

Step 1: Clean Your Canvas Workspace

To focus entirely on bulk dataset collection and looping mechanics, we will start by removing the intermediate condition logic from our previous build.

  1. Open your active Noca Flow canvas workspace.

  2. Click directly on your existing Condition Block (Is Active?) to highlight it.

  3. Press Delete on your keyboard, or click the trash icon.

  4. When the verification modal pop-up window appears asking how you want to proceed, select Delete node and all connected actions to cleanly wipe the old pathway branch, then click Delete.

Step 2: Convert Your Source Node to a Bulk Fetch Request

Modify your integration filter rules to pull down a complete collection list of all available accounts from your CRM instead of a single, hardcoded entry.

  1. Click on your root Salesforce Read Account Node to display its configuration drawer on the right.

  2. Scroll down to find the Condition filtering dropdown matrix section.

  3. Create a new conditional fetch rule by configuring the parameter fields as follows:

    • Field Selector: Select Account ID

    • Operator Dropdown: Choose Is Not Empty

  4. Result: By defining that the Account ID must not be empty, you transform your standard request into an open database sweep. Noca will now query your CRM and pull down a complete collection list array containing every single available account.

Step 3: Embed the Looping Logic Container

With your bulk list successfully gathered, place an execution loop onto your timeline to iterate over the dataset rows sequentially.

  1. Hover your cursor over the connection terminal line trailing right out of your Salesforce block.

  2. Click the trailing + icon that appears to splice in a new utility step.

  3. In the action catalog search box, type Loop, select the native Loop engine block from the logical utilities section, and click Insert.

  4. Result: A visual looping container boundary will materialize directly onto your workspace canvas.

Step 4: Configure Iteration via Object Parameters

Instruct the loop engine how to read and step through your incoming Salesforce list.

  1. Click on the newly placed Loop Node header to open its right-hand properties panel.

  2. Under the rule configurations section labeled “Loop number of times by”, select the Loop by object radio button choice.

  3. Save your properties configurations.

💡 Next Steps Preview: With your looping container fully deployed and listening for an object array, you are ready to drag your downstream destination action nodes (like Monday.com item creation blocks) straight inside this container. This setup will instruct Noca to dynamically spin up separate, individual items for every single account record found in the collection.

Key Takeaways

  • Bulk Collection Queries: Setting criteria filters like ID Is Not Empty shifts your integration nodes from isolated object fetches to pulling broad, multi-row datasets down onto your canvas.

  • Iterative Loop Containers: Selecting Loop by object builds a repetitive automated wrapper that steps through complex variable arrays row-by-row, keeping bulk migrations structured and predictable.

Fantastic job completing this bulk looping configuration exercise! You are now fully prepared to scale data management workloads across the Noca Flow ecosystem. Keep up the phenomenal momentum!