GoHighLevel Workflows Get Loop, Router and AI Agent Skills: What Each One Does and How to Set It Up

Status check: all three are listed as new releases under Automations on HighLevel's changelog. The entries don't mention Labs or a beta. I haven't tested them in my own account yet, so this is based on HighLevel's release notes. If you don't see them in your workflow builder yet, check the changelog entries linked below or ask HighLevel support.

The three updates at a glance

Loop: one trigger, many records

A single trigger often carries more than one record: the services in a request or the products in an order. Before this, handling each one meant code or a long workaround. The Loop action runs the steps inside it for every item.

• Loop Over: pick A list of items or A range of numbers.
• Items from any earlier step: pick the list with the tag icon, for example an array from an Inbound Webhook.
• Loop Item: inside the loop, open Custom values > Loop Item to map the current item's fields into any action.
• Range of numbers: set a Start Number and an End Number. The panel tells you how many times the actions will run.
• Execution Mode: Sequential by default. Turn on Parallel to run several iterations at the same time.
• Results for every iteration: the Test tab on the Loop step shows each iteration, each action inside it and its status.

How to set up a Loop (steps from HighLevel)

1. Go to Automation > Workflows and open a workflow.
2. Click the + icon where the loop should start, then select Loop.
3. Under Loop Over, choose A list of items or A range of numbers.
4. For a list, click the tag icon in Items and pick the list from a previous step. For a range, enter a Start Number and an End Number.
5. Set Execution Mode: leave it off for Sequential, or turn it on for Parallel (optional).
6. Click Save action.
7. Click the + icon inside the dashed loop box and add the actions you want to repeat. Use Custom values > Loop Item to fill their fields.
8. Save and publish your workflow.

HighLevel's example: one webhook, three opportunities

A service request form sends one webhook per customer with a list of services inside it: roof repair, gutter cleaning and exterior painting. The Loop goes over that list, and inside it are Create or update opportunity (name and value from the Loop Item), Add task (due date from the Loop Item) and Add notes. One test run creates three opportunities, three tasks and three notes, and the Test tab shows 3 items, 3 succeeded, 0 failed.

Good to know

• Only the actions inside the dashed loop box repeat. Actions below the box run once, after the loop finishes.
• A range loop has no list items, so Loop Item fields are empty. Use the loop counter under Loop Item to get the current number.

A practical use: any time a webhook from a booking tool, an order system or a multi-select form carries several line items, build the steps once inside a Loop instead of copying them or sending the data to an outside tool first.

Router: every matching branch, not just the first

The Router action sits in the same family as If/Else, with one big difference. If/Else stops at the first branch that matches. Router checks every branch and runs each one that matches, one after another, left to right.

• Custom rules: the branch runs only when its conditions match. You set them under Only continue if, with the same fields, operators and rule groups you know.
• Always run: the branch runs for every contact, with no conditions.
• Fallback: the branch runs only when no other branch matched.
• Order: drag a branch in the Branches list to make it run first.
• Testing: Test workflow on a real event lists every branch condition as passed or not, with the reason and the actual value the contact had.

How to set up a Router (steps from HighLevel)

1. Go to Automation > Workflows, open a workflow and add the Router action.
2. Open a branch and choose the branch type: Custom rules, Always run or Fallback.
3. For Custom rules, set the conditions under Only continue if.
4. Click Add branch for each path you need.
5. Drag the branches in the Branches list to set the run order (optional).
6. Add the actions that should run inside each branch.
7. Save the action, test it on a real event, then save and publish the workflow.

HighLevel's example: one form, three teams

A home services form asks "What service do you need?" and the lead can pick HVAC, Plumbing, Electrical or Carpentry. The Router has a branch for HVAC, Plumbing and Electrical, plus a Fallback. A lead who picks HVAC, Plumbing and Electrical would only reach the HVAC branch with If/Else. With Router, all three branches pass and each team gets the lead with its own note, notification, tag or task.

Two things HighLevel points out: branches run one after another, not at the same time, and a Fallback branch runs only when no other branch matched. For agencies, the win is fewer duplicate workflows. One Router replaces the copies of the same logic you built to catch a second or third match.

Skills in the AI Agent action

The Skills update lets the AI Agent action in workflows learn reusable procedures. You write a skill once, keep it in your library and attach it to any AI Agent action.

• Where: a Skills section sits right below Tools in the AI Agent action. It stays collapsed until you open it.
• Create with AI: the AI Assistant asks what the skill should do, when it should fire and what it must never do, then drafts the full skill for you to review. Nothing is saved until you choose Create.
• Write skill instructions: fill in Name, When should the agent use this? and Instructions, with Enhance Prompt to improve the wording.
• Add existing skill: search your library, read any skill in full, then attach it.
• Four built-in skills: Humanizer (removes the known signs of AI writing), Write-well (clear, simple, direct messages), Cold-email (first touch and follow-up emails to leads who haven't replied) and Sms-writer (short, human text messages).
• Loaded only when relevant: on every run the agent reads only each skill's name and its When should the agent use this? line. Full instructions load only when the run matches, and several matching skills can load together.

How to add a skill (steps from HighLevel)

1. Go to Automation > Workflows, open a workflow, then add or open an AI Agent Action.
2. Scroll down to Skills and expand it.
3. Click + Add skill and choose Create with AI, Write skill instructions or Add existing skill.
4. Review the skill, then click Create & attach or Attach.
5. Save the action.

HighLevel's example: one agent, every kind of lead

A heating and cooling company follows up every quote request with an email and a text. The AI Agent action has Send email and Send SMS as tools, plus the Cold-email and Sms-writer skills and a custom skill for emergency requests that fires when a lead reports no heat, no cooling, a gas smell or a water leak. A routine quote request gets a friendly email and a short text, a "no heat since last night" lead gets a same day slot, and a gas smell report gets safety steps first. Same agent, same instructions, different behaviour for each situation.

Good to know before you share skills across agents

• Skills are shared. An edit to a skill applies to every action that uses it.
• Detach vs Delete: Detach removes a skill from one action. Delete removes it from your library and from every action that uses it.
• Skills don't add tools. A skill tells the agent how to do something; the agent still needs the right tools, such as Send SMS, to act on it.
• Knowledge bases: a skill can use one. Name the knowledge base in the skill instructions and add the Knowledge base search tool to the action.

A practical setup for client accounts: keep the AI Agent's main instructions short, move the rules that only apply some of the time (emergencies, complaints, pricing questions to hand to a human) into separate skills, and attach Humanizer to anything that sends a message. Because an edit to a shared skill reaches every agent using it, test changes on one workflow before rolling them out.

Putting the three together

These fit nicely in one workflow: an Inbound Webhook brings in a list, a Loop handles each item, a Router sends the contact to every team that should act, and an AI Agent action with Skills writes the right follow-up for each situation. If you want to see where workflows fail once they get bigger, my Workflow Maps guide covers the errors view, and my Workflows API and MCP guide covers asking an AI assistant what broke.

For the rest of this week's HighLevel news, see my running LevelUp 2026 roundup.