Workflow Loop Repeat Limiter Step
B
Brady Bell
Adding a Loop Repeat Limiter Step within the workflows would be awesome. This feature would provide the ability to establish a loop that executes a set number of times (x amount) per contact before diverting to an alternative path.
This would offer improved control over loop processes and expand the functionality of our workflows. For instance, it could enable sending of emails or SMS 2 or 3 times until they are opened, allow for looping conversational AI 2 or 3 times if it times out, and many other possibilities. This enhancement would significantly enrich our workflow management capabilities.
Log In
S
Sales & Marketing
Merged in a post:
For Loops
B
Brian Clark
Some way to make if/else statements act like a for or foreach loop.
S
Sales & Marketing
Merged in a post:
Built-in Loop Action Inside Workflows
I
Ido Havazelet
Proposal to add a Loop action inside Workflows, similar to the functionality available in Zapier, including enhanced follow-up logic for calls and messages.
What the Loop action would enable:
- Repeat a single action or a group of actions a defined number of times.
- “Repeat Until” logic — loop until a specific condition is met.
- Loop through a list/array of items (e.g., Custom Objects, multiple phone numbers, alternate contacts).
- Safety controls to prevent infinite loops, with max iterations and timeout settings.
Follow-up Use Cases for Calls & Messages:
- Automatic call follow-up:
Continue calling a contact every X minutes/hours until they answer, stop after Y attempts, or stop when a tag/field changes.
- Missed call workflow loops:
If the contact misses a call, loop through a follow-up sequence (SMS → email → voicemail drop → wait → retry call).
- Message-based follow-up:*
Repeat a sequence of SMS/email attempts until the contact replies, clicks a link, or reaches a specific conversation status.
- Multi-channel loops:
For example:
1. Try SMS → wait for reply
2. If no reply, try email → wait
3. If still no engagement, try call
4. Repeat the full cycle up to N times
- Looping until conversation outcome:
Continue outreach until the lead schedules an appointment, responds with a keyword, or marks themselves as “Not interested.”
Why this is important:
- Enables advanced automation behavior currently impossible inside GHL.
- Greatly improves follow-up efficiency for sales teams.
- Removes the need for Zapier/Make loops or custom-coded workarounds.
- Reduces lead leakage and increases conversion rates.
Additional use cases:
- Repeated attempts to verify a phone number or request missing info.
- Progressive reminders until a form is completed.
- Follow-up escalation (e.g., after 3 failed attempts, notify team member).
A built-in Loop action would significantly elevate HighLevel’s automation capabilities, especially in call and message follow-up workflows.
A
Ashwin Raghunandan
Merged in a post:
I'd love love love a limited loop feature.
A
Antigone Klima
I spend a lot of time figuring out how to "fake" this using what's available, and there's always complications.
For reals, can we get an option in the If/Else or create a Count/Loop function, please?
For example, IF this is the first time through the loop, send this message and do these things. If it's the second time through, do these other things. And so on. Then when the COUNT is reached, exit the loop.
Providing this functionality is quite cumbersome because of all the games I have to play to trick the system into thinking it's own way.
Even the ability to recursively update a field or would help, such as setting the event date to current event + 1 day so that I don't have to have one custom value for each date of the masterclass/summit/challenge when the client wants to have it again OR do some ginormously long linear workflow that's impossible to maintain because you can't figure out which ACTION box holds whatever it is you need to change.
Or the recursive field can be a number. For example, the down payment is $5,000. So loop until total of payments received meets or exceeds $5,000, THEN move to the next step. At the moment we use a custom field that gets manually updated by Sales or Accounting whenever a payment is made.
S
Sebastian Miller
This would be nice, I have found a way to do this, but it takes too many steps.