We’ve added a new toggle in the Workflow Builder that lets you open the common HighLevel sidebar directly from within workflows. This gives you quick access to other products, tools, and pages without leaving the builder. You can also use the keyboard shortcut Cmd+\ (Mac) or Ctrl+\ (Windows) to quickly show or hide the sidebar.

Use the toggle in the top-left corner of the Workflow Builder to show or hide the standard HighLevel navigation sidebar. The same action can be triggered using the keyboard shortcut. When enabled, the familiar HighLevel sidebar appears, giving you seamless access to other areas of the platform.

Users switch between workflows and other areas of HighLevel while building automations. This update reduces navigation friction, improves accessibility, and brings a more consistent experience across the platform.

You can now select TikTok Interactive Messenger as a reply channel in the Wait → Until the contact replies workflow action. This enhancement allows workflows to pause and resume based on a contact’s reply through TikTok DMs.

When a workflow reaches a Wait Until the Contact Replies step, you can choose TikTok Interactive Messenger under Reply to. The workflow will continue only after the contact responds through TikTok DM.

Businesses using TikTok for customer engagement need reply-based automation across all messaging channels. This update brings TikTok DMs into the same workflow experience, making it easier to build conversational automations and follow-up sequences.

A fitness studio sends a TikTok DM inviting prospects to claim a free trial. The workflow waits for a reply through TikTok Interactive Messenger before sending the next message or assigning the lead to a team member.

Automatic Mandate Creation at Signup — The affiliate signup page now creates the payment method before the $1 auth charge. This ensures the card is set up correctly in Stripe, which then automatically creates the e-mandate for Indian cards.

Overridden Mandate Params for India (Tax Inclusion) — Mandate parameters are overridden to include applicable tax amounts for India, ensuring compliance with RBI e-mandate requirements for Indian recurring payments.

Mandate Confirmation Option in Billing Page — Post-signup, customers with Indian cards will see a new section in the subscription/billing page to confirm their mandate. This triggers the 3DS flow that registers the e-mandate, enabling seamless future renewals.

Indian card signups would complete, but automatic renewals would fail — the card would convert but silently not bill on renewal.

No RBI e-mandate was being created, making recurring charges non-compliant and causing payment failures.

Payment method is created first at signup, allowing Stripe to automatically set up the e-mandate for Indian cards.

A dedicated billing page option allows customers to confirm the mandate post-signup via 3DS.

Renewals for Indian cards succeed without additional per-cycle OTP friction for amounts under ₹15,000.

For amounts above ₹15,000, mandate is also created but customers will need to pre-approve each charge monthly when their bank sends a pre-debit notification.

Signup UX remains unchanged — zero additional friction for the customer.

Sign up for an agency subscription via affiliates.gohighlevel.com or gohighlevel.in using an Indian-issued card — mandate is auto-initiated during signup.

After signup, navigate to the Billing page — a new mandate confirmation section will be visible for customers with Indian cards.

Click Confirm Mandate — a 3DS popup will appear to authorize the e-mandate.

Once confirmed, future renewals will process automatically (without additional authentication for amounts under ₹15,000; pre-debit bank notification approval required for amounts above ₹15,000).

This applies only to Indian-issued cards on agency subscriptions signed up via affiliates.gohighlevel.com or gohighlevel.in as of now.

If mandate is not confirmed, it will default to earlier behavior (automatic renewals will fail, user needs to renew on session)

Non-Indian card behaviour remains unchanged.

Based on the response we received we have added a multiple actions and triggers for Housecall Pro.

The Housecall Pro integration in Workflows now spans the full field-service lifecycle. Nine triggers — covering jobs, estimates, leads, and customers — and fourteen actions across customer, job, estimate, lead, and job-appointment management let home service businesses react to operational events and drive Housecall Pro from any workflow.

All triggers poll Housecall Pro on a fixed cadence: creation events (Job created, Estimate created, Lead created, Customer created) every 5 minutes, and schedule, finish, and cancel events (Job scheduled, Job finished, Job canceled, Estimate scheduled, Estimate finished) every 10 minutes. Actions cover the full CRUD surface for customers and customer addresses, full job and job-appointment management, estimate creation and retrieval, and lead creation and retrieval. Authentication is API key — connect once, target multiple accounts via the Connected Account dropdown.

A homeowner submits a ‘Request a Quote’ form on the website. The workflow creates the matching Housecall Pro lead via Create a lead, pings dispatch with the lead context, and tags the CRM contact. Two days later, the office books an estimate visit — Estimate scheduled fires and the workflow sends the customer a reminder with the technician’s ETA. The technician completes the estimate; Estimate finished fires and the workflow sends the customer a link to review and approve the quote. Once approved, the workflow uses Create a job to spin up the job, and the cycle continues through Job scheduled, Job finished, and the post-service follow-up.

We've launched a new dashboard in the Agency UI — giving you full visibility into your domain's sending health and sub-account performance in one place.

Agencies created on or after April 27, 2026. Existing agencies are unaffected — a migration plan is coming by end of Q2 2026.

📖 Full guide here

You can now connect Calendly directly to Workflows. Five triggers — Invitee created, Invitee canceled, Invitee no show created, New routing form submission, and Event cancelled — plus nine actions covering one-off meeting creation, invitee booking, event lifecycle management, no-show marking, and Calendly contact and user lookups let your automations react to scheduling activity and drive Calendly back the other way.

Four of the five triggers are instant — backed by Calendly’s native webhooks (invitee.created, invitee.canceled, invitee_no_show.created, routing_form_submission.created). The fifth (Event cancelled, for host-initiated cancellation) polls every 5 minutes because Calendly does not emit a native webhook for it. Each instant trigger exposes a Webhook Subscription Scope filter — User to watch the connected user’s events, or Organization to watch every user in the Calendly org. Authentication is OAuth via an External Authentication Configuration step that labels each connected account with a friendly Name and Email.

A prospect books a discovery call through a sales rep’s Calendly link. Invitee created fires within seconds — the workflow finds or creates the matching CRM contact, attaches the booking details (event type, scheduled window, custom question answers) to custom fields, and sends a pre-call SMS with prep material. If the prospect later cancels, Invitee canceled fires; the workflow waits two hours, then sends a tailored reschedule offer with a one-off Calendly link.

We’ve added a new to help eligible WhatsApp subscribers switch to the .

This banner appears in Conversations, making it easier for users to discover and adopt MMLite while actively managing WhatsApp chats.

## What’s New ✨

Eligible WhatsApp subscribers will now see a banner in Conversations prompting them to move to the MMLite API version.

This complements the existing banner on the page, creating another touchpoint to drive awareness and adoption.

## Why It Matters 🎯

Switching to the MMLite API version can help improve WhatsApp messaging performance for customers using HighLevel.

It also supports more efficient WhatsApp messaging infrastructure, helping HighLevel optimize messaging costs at scale.

## Benefits 📊

* Better visibility for MMLite adoption inside Conversations 👀

* Improved WhatsApp delivery performance for customers ⚡

* More efficient WhatsApp messaging infrastructure 💰

* Additional adoption touchpoint alongside the WhatsApp Services page 🔁

## Availability ✅

The MMLite adoption banner is now available in Conversations for eligible WhatsApp subscribers.

We've significantly improved the time it takes to open workflows from the Workflow list, making the transition into Workflow Builder much faster. In many scenarios, initial workflow load times are up to 4x faster, helping you get into your workflows with less waiting.

Behind the scenes, we've optimized how Workflow Builder resources are loaded and rendered. This helps workflows and builder components become available faster, creating a more responsive experience from the moment you open a workflow.

One of the most requested enhancements to the SaaS Configurator is here.

We've increased the maximum number of SaaS Plans and SaaS Categories from 20 to 99, giving agencies significantly more flexibility to build, organize, and scale their SaaS offerings.

As agencies grow, their pricing strategies often become more sophisticated. Many agencies need separate plans for different industries, service levels, locations, customer segments, onboarding packages, add-ons, or bundled offerings. The previous limit of 20 plans and categories made it challenging to support these evolving business models at scale.

With this release, agencies can now create and manage up to 99 SaaS Plans and 99 SaaS Categories, making it easier to build a more comprehensive product catalog without running into platform limitations.

📈

You can now create up to 99 SaaS Plans, allowing you to:

📊

You can now create up to 99 SaaS Categories, providing greater flexibility to organize and manage a larger portfolio of plans.

This makes it easier to group plans by:

Many agencies have outgrown the previous limits and have been looking for more flexibility to support increasingly complex SaaS businesses. Whether you're creating industry-specific packages, testing new pricing models, building regional offerings, or managing a large portfolio of services, this update removes a major scalability constraint.

You now have the freedom to build a SaaS catalog that matches the way your business operates today—and the flexibility to continue growing tomorrow