Repeat Actions Over a List (Looping)

Monday, November 16, 2026

Sales HubMarketing HubService HubContent HubData HubSmart CRMRevenue HubStarterProfessionalEnterprisePrivate beta

What it is

A Repeat container in the Agent Hub workflow builder runs a set of actions for each record in a list, or a set number of times (up to 100).

Why it matters

Acting on a list used to require workarounds. Repeat runs a full sequence, including branches, on every record.

The Take

Joshua Oakes

My pattern library in my head is entirely founded on a world without this.
— Joshua Oakes

Per the panel, Repeat Actions Over a List (Looping) adds a Repeat container to the Agent Hub workflow builder. It runs a set of actions once for each record in a list, or a set number of times, up to 100. Actions inside the container run in order for each item, and actions below it run after the loop finishes. It is in private beta, for Starter through Enterprise on Sales, Marketing, Service, Content and Data Hub, and for Professional and Enterprise on Smart CRM and Revenue Hub. The point of the Why text: acting on a list used to take building around the gap, or pointing a single action at a list with no per-item logic, and Repeat runs a full sequence, branches included, on every record. One cost line from the update text as Chris read it: each repeat uses credits for every record processed, so total usage depends on the size of your list.

Chris raised it and called it "a bombshell update." His framing: "If you've been avoiding going to build workflows or automation over in Agent Hub land, this is what that starts to look like." He read the What; Oakes read the Why and carried most of the talk. Oakes's first reaction was to the Why's own example, an agent reviewing each stale deal and then a task being created for it: "I think that's probably a pretty bad example because you would just enroll a list of the deals … with the logic and then it would create a task on the deal."

On the name, Chris: "Of course, we need a different word to describe what everybody is asking for." Then, once he had read through it: "Users are never … say, can you create a for loop right here? I need a workflow with a for loop in it, right? So repeat is probably the right word, so that you can just say, oh, how do we repeat this with this list? And now AI is going to know where it can go to do that." After Chris read the list-input-or-up-to-100 options, Oakes: "So it's not a while loop to use." On who gets it, Chris read "It's down to starter level" and Oakes explained why: "it comes down to starter because these are going to be purely credit priced workflows, not hub or tier constrained workflows."

Why it lands for builders: Chris asked how long the community has wanted this, and Oakes's answer was personal: "I have Stockholm syndrome or something because … it's been so far off the table of ways to solve problems that … my pattern library in my head is entirely founded on a world without this." Chris: "It's like your for loop namespace does not include the word HubSpot in it." Oakes then described what he builds today: "we're going to have a list of lists and then we're going to have a workflow that branches and it rolls a separate workflow."

Custom code and credits. Chris asked, "Were we ever using custom coded actions to help with stuff like this?" Oakes: "Yeah, for sure." When this reaches public beta, or general availability, he said the workflow action filter is what he will look for: "do we have anything in this portal where we can replace this or where it makes sense to replace this." His open question is cost: "It'll be interesting to … see what credit consumption across custom code action versus these loops will look like, and it depends on what kind of actions you are performing, I suppose, within the loop more than anything." Chris tied it to Breeze: "This will be probably a great example of why we want you to start talking to Breeze inside of HubSpot, especially if you get into this beta." His reasoning was that when you ask Claude or GPT about loop-like things, "it's going to point you to much more complex solutions."

Associations and buying groups. Oakes named the place he most wants to test it: "the number one place where acting on records, fetching, setting or retrieving, or comparing information properties, etc. is where a loop like that is necessary," with the example "deal reaches a certain stage, check all of the associated people in the buying group for something." His caution: "I hope Breeze is really good at these because it's in an area where describing those requirements is hard for beginners and advanced users." His illustration, which he called "nonsensical, but as an example": when the deal reaches quoting, make sure everybody on the deal has an executed NDA. Today the way to do it is "sync properties with crazy requirement conditional dependencies," where the loop version is to "just check everything and then send the reminder email if they haven't executed the NDA." He called that "the here be dragons area of my HubSpot map," the workflows that run on the contact and change the deal, or the reverse, versus "just check all the associate records."

What to do: if your portal is in the Agent Hub private beta, try Repeat on one small list first and work out what a single record costs in credits before you point it at a real one. If you are not in the beta, there is nothing to set up. Nothing read on air said when it moves past private beta. The useful work now is Oakes's inventory: list the workflows that use custom-coded actions, a list of lists, or contact and deal workflows that trigger each other, so you know what Repeat might replace and what it would cost to run it.

Watch Us Discuss This

The full segment from the show, us working through this update start to finish.

Repeat actions over a list: looping lands in Agent Hub, and the workarounds it retires10:35

Produced by Value-First Media