New Loop Workflow Action Iterates Over Lists and Number Ranges

TL;DR

HighLevel added a native Loop action to workflows that repeats actions across array items or numeric ranges. If you process incoming webhooks with multiple items, you can now handle those iterations directly in the workflow builder.

Who this affects

HighLevel has not confirmed which plans or sub-account types have access to this feature, nor whether any plan gating applies. Anyone managing automations that ingest lists or external arrays will want to review it.

What changed

• Added a new Loop action inside workflows that can iterate over "A list of items" or "A range of numbers".
• Allowed selecting list items from earlier workflow steps, including data arrays received through an Inbound Webhook.
• Added "Custom values > Loop Item" to reference the current item fields or loop counter within actions placed inside the loop.
• Added configuration inputs for numeric iterations using Start Number and End Number.
• Introduced execution modes that let actions run sequentially by default or concurrently in parallel.
• Added a visual dashed loop box inside the builder; actions inside the box execute per iteration, while actions below the box execute once after the loop finishes.
• Added a Test tab on the Loop step showing iteration details, execution status, and individual action results.
• HighLevel has not confirmed rollout status, plan gating, or specific execution limits.

Where to find it

In your sub-account, navigate to Automation > Workflows. Open a workflow or create a new one, then add an action and select Loop from the action menu.

How agencies will use this

Take an Inbound Webhook trigger that receives order details containing a list of line items. An agency can now add a Loop action, select the array from the webhook trigger data, and choose sequential execution. Inside the dashed loop box, you can add actions that reference "Custom values > Loop Item" to map product names, quantities, or line-item IDs into specific workflow steps for each entry in that list. Once the loop finishes processing all items, the workflow exits the dashed box to execute the final steps below it, such as sending an internal notification that the batch is complete.

Our take

This is a major addition for anyone building complex automations. Bouncing array data to third-party tools just to iterate over line items or repeated records has been a persistent friction point in HighLevel workflows. Native looping, paired with a dedicated Test tab and parallel execution options, brings the workflow engine much closer to a full automation environment. If you handle webhook payloads with arrays, test this in a staging workflow to see if you can retire external middleware.