You can now send one contact down every branch it matches. 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.

What's New

Every matching branch runs

• Earlier, If/Else sent the contact into the first branch that matched and skipped the rest, even when the contact matched them too.
• Now the Router action sends the contact into each branch whose conditions match.

Three branch types

• Custom rules: The branch runs only when its conditions match.
• Always run: The branch runs for every contact, with no conditions.
• Fallback: The branch runs only when no other branch matched.

Conditions you already know

• Set the rule under Only continue if. Pick any field, choose an operator, and add more conditions or rule groups as needed.
• Add as many branches as your use case needs.

You control the order

• Branches run left to right. Drag a branch in the Branches list to make it run first.

Test it on a real event

• Test the Router action with Test workflow on a real event.
• The output lists every branch condition as Passed or not, with the reason and the actual value the contact had.

How to Use

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

Worked Example: One Form, Three Teams

A home services business asks one question on its form: "What service do you need?" The lead can pick more than one: HVAC, Plumbing, Electrical, or Carpentry.

The Router action has four branches:

1. Branch 1: the service includes HVAC.
2. Branch 2: the service includes Plumbing.
3. Branch 3: the service includes Electrical.
4. Branch 4: Fallback, for leads that match no other branch.

A lead picks HVAC, Plumbing, and Electrical. With If/Else, only the HVAC branch would run. With Router, the test output shows Branch 1, Branch 2, and Branch 3 all passed, each with its reason. Every team gets the lead, and each branch runs its own next steps: a note, an internal notification, a tag, a task.

Why This Matters

Real leads rarely want just one thing. Router lets one workflow act on every match instead of only the first one.

• No duplicate workflows: One Router replaces the copies of the same logic you built to catch a second or third match.
• Predictable order: Branches run left to right, so you decide what happens first.
• Proof before you publish: The test output shows which branches passed and why.

One contact, every matching branch, in the order you choose.

Good to Know

• Branches run one after another, not at the same time.
• A Fallback branch runs only when no other branch matched.

You can now repeat a set of actions for every item in a list, right inside a workflow. The Loop action runs the actions inside it once for each item, or once for each number in a range. One trigger, many records, no code.

What's New

• Loop Over: Pick "A list of items" or "A range of numbers". An "i" tooltip explains every field.
• Items from any earlier step: Pick the list with the tag icon, such as 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, one iteration after the other. Turn on Parallel to run several iterations at the same time.
• Results for every iteration: The Test tab on the Loop step shows every iteration, every action inside it, and its status.

How to Use

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. This step is 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.

Worked Example: One Webhook, Three Opportunities

The goal: a service request form sends one webhook per customer, with a list of services inside it. You want one opportunity, one task and one note for every service.

1. Trigger: Inbound Webhook. The services list holds three items: Roof repair, Gutter cleaning and Exterior painting.
2. Loop: Loop Over = A list of items. Items = the services list from the webhook.
3. Inside the loop: Create or update opportunity, with Opportunity Name = Loop Item > Name and Opportunity Value = Loop Item > Estimated Value.
4. Inside the loop: Add task, with Due date = Loop Item > Preferred Date.
5. Inside the loop: Add notes, with Note = Loop Item > Urgency.

One test run. The loop runs three times and creates three opportunities, three tasks and three notes. The Test tab shows 3 items, 3 succeeded, 0 failed.

Why This Matters

A single trigger often carries many records: the services in a request, the products in an order. Earlier, handling each one meant code or a long workaround. Now you build the steps once and the Loop runs them for every item.

Range mode covers the other case: run a set of actions a fixed number of times, 5 or 10, with no list at all. Parallel mode keeps loops fast when the actions call external systems. Build once, run for every item.

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.

You can now work with your workflows from your AI assistant. Workflows in the LeadConnector MCP server, now in private beta, let Claude, ChatGPT, Cursor and other AI tools find workflows, explain what failed and for whom, count enrollments, and build and publish workflows for you.

✅ What's New

• Find workflows – Search by name, status, folder or date.
• Read workflows – Read a workflow's full definition: triggers, steps, branches and settings.
• Build workflows – Create a workflow from a description. The assistant checks it for errors and saves it as a draft.
• Update and publish – Change a workflow, publish it, or set it back to draft.
• Delete workflows – Delete a workflow, with an extra confirmation first.
• Execution logs – See who entered a workflow, what happened at each step and which steps failed, with the error.
• Statistics – Count enrollments, completions and failures per step, by hour, day or week.

🚀 Why This Matters

With workflows in the LeadConnector MCP server, you can:

• Answer "what broke, and for whom?" with one question instead of reading execution logs by hand.
• Get a first draft of a workflow by describing it.
• Check how your workflows are performing from the AI tool you already use.

💡 Example Use Cases

Failure triage

Ask which steps in New Lead Nurture failed this week → the assistant reads the logs → it lists each failed step with the contact and the error.

Weekly numbers

Ask how many contacts entered Webinar Follow-up each week this month → the assistant counts enrollments by week → you get one number per week.

Draft by description

Describe a workflow that tags new contacts webinar-lead and sends a welcome SMS → the assistant checks it for errors → it saves a draft for you to review in the builder.

🔌 How to Get Started

1. Add the LeadConnector MCP server to your AI tool. In Claude, go to Settings → Connectors → Add custom connector and enter <a href="https://services.leadconnectorhq.com/mcp/anthropic/v2" rel="ugc nofollow noopener noreferrer" target="blank”>https://services.leadconnectorhq.com/mcp/anthropic/v2. In ChatGPT, turn on Developer mode, open ChatGPT Plugins and add <a href="https://services.leadconnectorhq.com/mcp/openai/v2/" rel="ugc nofollow noopener noreferrer" target="blank”>https://services.leadconnectorhq.com/mcp/openai/v2/ as the connection. Cursor uses <a href="https://services.leadconnectorhq.com/mcp/cursor/v2" rel="ugc nofollow noopener noreferrer" target="blank”>https://services.leadconnectorhq.com/mcp/cursor/v2.
2. Sign in with your LeadConnector account, choose the sub-account and approve the workflow permissions.
3. Start a new chat and ask about your workflows. The <a href="https://marketplace.leadconnectorhq.com/docs/other/mcp" rel="ugc nofollow noopener noreferrer" target="blank”>LeadConnector MCP server docs have setup steps for every client.

⚠️ Notes & Details

• Private beta: workflows in the MCP server work in sub-accounts enabled for the Workflows API. Others get WORKFLOWAPINOTENABLEDFORLOCATION. Contact support to join.
• New workflows are created as drafts. Publishing is a separate request.
• To change a published workflow, it's set to draft first. While it's a draft, its triggers are off and contacts in it are paused.
• Each request works in one sub-account. Agency connections that cover several sub-accounts are rolling out.
• Deleting a workflow is permanent and stops everyone currently in it.
• Logs cover up to 30 days per request and go back 60 days. They show live runs; test runs from the builder aren't included.

Support doc <a href="https://help.leadconnectorhq.com/support/solutions/articles/155000009504" rel="ugc nofollow noopener noreferrer" target="blank”>Here

You can now build and manage workflows from your own code. The new Workflows API, now in private beta, creates, reads, updates, publishes and deletes workflows, and reads each workflow's execution logs and statistics.

✅ What's New

• Create workflows – Create a workflow from a complete definition. New workflows start as drafts.
• Read and update workflows – Read any workflow as a definition you can change and send back.
• Validate before saving – Check a definition for errors without saving it, with each error pointing at the exact step.
• Publish or unpublish – Publish a workflow, or set it back to draft.
• Search and delete – Find workflows by name, status, folder or date, and delete workflows.
• Step types – Browse every trigger and action available in the sub-account, with its fields.
• Execution logs – See who entered a workflow, what happened at each step and which steps failed, with the error.
• Statistics – Count enrollments, completions and failures per step, by hour, day or week.

🚀 Why This Matters

With the Workflows API, you can:

• Roll out the same workflow to many sub-accounts without rebuilding it by hand.
• Catch failing steps from your own monitoring instead of opening each workflow.
• Let your own app or AI agent build workflows for your clients.

💡 Example Use Cases

Standard rollout

Read a workflow from your template sub-account → create it in each client sub-account → publish it.

Failure report

Every Monday, count failures per step for your key workflows → list who was affected → send the summary to your team.

Onboarding from your app

A client signs up in your product → your app creates and publishes their onboarding workflow in their sub-account.

🔌 How to Get Started

1. In the sub-account, go to Settings → Private Integrations, create an integration and select the workflow scopes you need: View Workflows, Edit Workflows, Publish Workflows, Delete Workflows and View Workflow Logs.
2. Send the token as a bearer token, with the Version: v3 header and the sub-account's locationId on every request.
3. Use the <a href="https://marketplace.leadconnectorhq.com/docs/leadconnector/workflows/workflows-api-v-3" rel="ugc nofollow noopener noreferrer" target="blank”>Workflows API reference for every endpoint and its fields. Each endpoint page has a request panel to try it with your token.

• Private beta: the Workflows API is enabled for selected sub-accounts. Others get a 403 with WORKFLOWAPINOTENABLEDFORLOCATION. Contact support to join.
• Updates replace the whole workflow, so read it first and send back the version you read.
• To edit a published workflow, set it to draft first. While it's a draft, its triggers are off and contacts in it are paused.
• App steps only accept an app account that's already connected in the sub-account.
• Deleting a workflow is permanent and stops everyone currently in it.
• Logs cover up to 30 days per request and go back 60 days. They show live runs; test runs from the builder aren't included.

Support doc Here

📥 Overview

Your customers expect more than just text messages. They want engaging, interactive conversations that make it easier to connect with businesses.

That's why we're excited to bring RCS Messaging to Labs, giving agencies early access to richer, branded messaging experiences directly within HighLevel.

And getting started is now easier than ever! You can complete the entire RCS registration process directly within HighLevel, without navigating external provider platforms.

Simply enable RCS in Labs for the sub-accounts you want to onboard, and complete the guided registration process to start bringing richer messaging experiences to your customers.

📊 What's New?

✅ RCS Messaging Is Now Available in Labs

Agencies can enable RCS Messaging through Labs and choose which sub-accounts they want to onboard.

Start with a few clients, explore the experience, and expand as you're ready.

✅ Complete RCS Registration Without Leaving HighLevel

We've introduced a guided onboarding experience that walks you through everything needed to register your RCS sender.

Here's what the registration process looks like:

1. Brand Identity: Add your business name, logo, description, contact information, and website details. Preview how your brand will appear to customers.
2. Countries: Select the countries where you plan to use RCS messaging.
3. Sender Details: Tell us how you'll use RCS, what messages you'll send, and how customers give consent to receive them.
4. US Verification (if applicable): Provide additional business and messaging details if you're registering for the United States.
5. Review & Submit: Review your information and submit your registration for approval.

Your progress is saved automatically, so you can complete registration at your own pace.

Once submitted, you can track your sender's approval status directly in HighLevel.

✅ Bring More Engaging Experiences to Every Conversation

Once your RCS sender is approved, you can go beyond traditional SMS with:

• Branded Messaging: Display your business name and logo for a more recognizable experience.
• Rich Cards & Carousels: Showcase products, services, and offers with images and interactive content.
• Interactive Buttons: Help customers take action directly from a message.
• Suggested Replies: Make it easier for customers to respond with a single tap.

✅ Use RCS Across Your Existing HighLevel Tools

Bring rich messaging into the tools you already use:

• 1:1 Conversations: Connect with customers through interactive messages.
• Bulk Messaging: Reach multiple contacts with engaging RCS content.
• Workflows: Build automated customer journeys with rich messages and interactive actions.
• RCS Templates: Create and reuse rich content for consistent communication.

🧪 How to Enable RCS Messaging

Getting started takes just a few steps.

Step 1: Enable RCS in Labs

1. Navigate to Agency Settings → Labs.
2. Search for RCS Messaging.
3. Enable the feature.

Step 2: Start RCS Onboarding

1. Open the sub-account where you want to set up RCS.
2. Navigate to Settings → Phone System → RCS Messaging.
3. Start the guided registration process.
4. Complete the required details and submit your sender for review.

Once your sender is approved, its status will change to Live, and you can start using RCS messaging.

💡 Tip: You can enable RCS for multiple sub-accounts, giving you the flexibility to introduce rich messaging to different clients at your own pace.

🔍 Why It Matters

RCS brings a more engaging way to communicate with your customers while keeping everything within HighLevel.

💬 Make conversations more engaging: Go beyond plain text with rich cards, images, and interactive buttons.

🎯 Make it easier for customers to take action: Let them explore offers, respond to questions, and interact directly from their messaging app.

⚡ Get started with less effort: Complete registration and manage your RCS senders without leaving HighLevel.

🤝 Offer more value to your clients: Introduce richer messaging experiences across the sub-accounts you manage.

🚀 Grow at your own pace: Start with selected clients and expand as you're ready.

RCS isn't just about richer messages. It's about making every customer interaction more useful, engaging, and actionable.

💡 Good to Know

RCS Messaging is currently available through Labs.

RCS sender registrations require carrier and provider approval before live messaging can begin.

Availability depends on supported countries, carriers, and recipient devices.

You can save your registration progress and return to complete it later.

* You can add test devices to try RCS messaging before your sender goes live.

💬 Your Feedback Matters!

This Labs release is an important milestone in bringing RCS Messaging to more HighLevel customers.

As you explore the onboarding experience and start using RCS, your feedback will be crucial in shaping what comes next.

We'd love to hear what works well, what could be simpler, and what additional capabilities would make RCS even more valuable for your business.

Thank you for helping us build the next generation of messaging in HighLevel!