Step 5 · Parallel Branch
Count High-Discount Items
A second Collection Operation node, branching in parallel off Data Mapping's output — not part of the Loop's per-item chain.
Why a parallel branch instead of a counter inside the loop
Flow Studio's node set has no per-iteration "increment" primitive. Since the full mapped product list is already available before the Loop even starts, it's simpler and more reliable to pre-compute how many products qualify as "high discount" right here, save that number (next page), and read it back once the loop finishes — rather than trying to accumulate a count across iterations.
Configuration
| Field | Value |
|---|---|
operation | filter |
expression | item.discountPercent > 12 |
Note the field name: discountPercent — the Data-Mapping-renamed field from the previous page, not the original discountPercentage.
Result (with both sample products)
Only product 2 (18.19%) qualifies; product 1 (10.48%) doesn't:
{
"status": "success",
"successCount": 1,
"errorCount": 0,
"count": 1,
"items": [
{ "json": { "productId": 2, "productName": "EYESHADOW PALETTE WITH MIRROR", "discountPercent": 18.19, "...": "..." } }
]
}The count field (1 here) is what the next page (Memory Store) reads and saves for later.
Not yet built on the canvas
This node has not yet been added and screenshotted in the live workflow — the configuration above is the intended design, carried over unverified from planning. Confirm it once built.