Changelog
Follow up on the latest improvements and updates.
RSS
new
improved
Automations
New GPT 5.1 model in GPT action
What’s New?
We have introduced GPT 5.1 model in the GPT action in workflows
How to Use?
Click the "+" icon and search for "GPT powered by OpenAI"
Click on the "Model" field and select GPT 5.1
Pricing
- GPT 5.1 Input Cost : $1.250 / 1M tokens
- GPT 5.1 Output Cost : $10.000 / 1M tokens
Why to use GPT 5.1 ?
- Better and faster reasoning over GPT 5
- More conversational and warmer personality
- Better Instruction following over other OpenAI models
improved
Automations
Workflow Builder: Workflow header UI updates
We improved the Workflow Builder header so long names no longer overflow on the UI. The header now auto-scales, truncates with an ellipsis, and shows the full name on hover.
What’s new
- The workflow header now dynamically scales based on length.
- Very long names are neatly truncated with an ellipsis in the builder so the UI doesn’t break.
- Hover to reveal: Users can hover the header to see the full workflow name in a tooltip.
Why it matters
- No more layout issues with long workflow names.
- Cleaner, more readable builder experience.
Preview
new
Payments
Integrations
Adyen payments now Live (Cards, EU & North America)
What’s new?
We have added Adyen as a payment provider. Adyen is widely used across Europe and North America and is known for its enterprise grade capabilities.
With this launch, agencies can serve prospects and clients who prefer or already use Adyen, and those who can’t adopt other providers.
Scope at launch: Card payments (credit/debit)
How it works / What you need to do
- Have an Adyen account ready (with your merchant credentials).
- In your account, go to Dashboard → Payments (left nav) → Connect Adyen → Add Credentials for live/test → Save
- Assign Adyen as the default payment provider for the channels where you want to accept card payments.
- What credentials are needed?
- Live - Company API Key and Live URL Prefix - Details on Credentials
- Test/Sandbox - Company API Key
- You will need an active Adyen merchant account and approval from Adyen.
- Pricing, underwriting, and regional availability are determined by Adyen.
Why it matters
- Win more enterprise deals - Many larger companies standardize on Adyen - now you can meet that requirement.
- Supports 3DS type cards - Provides additional security and compliance for international and high-risk transactions.
- Stronger EU/North America coverage - Adyen’s footprint makes it easier to onboard clients operating in those regions.
- Faster client adoption - Existing Adyen merchants can connect their credentials and start taking card payments through your white‑label.
What’s next
- SaaS Mode integration: Soon, agencies will be able to use Adyen for SaaS Mode billing and subscriptions in the reseller/whitelabel flow.
- Beyond cards (exploratory): We’re evaluating additional Adyen supported payment methods for future phases like POS, card present, etc.
Visuals
Adyen on Payment Link
On payment integrations page
On click Connect button
Agency admins clicking Sell on Marketplace now skip the manual developer signup form. If no developer account exists, we auto-create a developer profile from existing details and take them straight to login.
✨ What’s new?
- Auto-detect when an admin has no developer account
- Instant backend profile creation from available account data
- Direct login flow: enter password → accept T&Cs → verify one-time password (email)
- Land directly in the developer account—no manual details to fill
💡Why it matters?
- This removes signup friction and reduces drop-offs, helping agencies list assets (like AI agents) faster and more reliably.
Who gets it
- All agency admins using Sell on Marketplace.
💻 How it works (before → after)
- Before: Click Sell on Marketplace → if no developer account, complete a lengthy manual signup → then login.
- Now: Click Sell on Marketplace → we auto-create the developer profile → login (password + T&Cs + OTP) → you’re in.
Security & compliance
- Standard T&Cs acceptance and one-time email OTP verification remain required.
What’s next?
- We’re continuing to streamline the developer journey to improve the sign-up → publish conversion rate and make publishing even more frictionless.
new
App Marketplace
API
Agency's Reselling Config API
🚀 Overview
We’ve released an API that lets app developers fetch the reselling prices agencies have set (including any markups) so they can display the correct, whitelabeled reselling price to the sub-account on custom pages or checkout flows.
✨ What’s new?
- Get Rebilling Config for App API to retrieve the current agency-set pricing for your app/meters.
- The response includes reselling rates across all pricing types - Subscriptions, One-time, Usage-based.
🧑💻 How to use it as a Developer
- Use the Sub-account token and call the Get Rebilling Config for App endpoint.
- Read the returned pricing configuration (agency’s upsold price for the relevant app/meter).
- Render those values on your custom pages—e.g., plan cards, paywalls, and checkouts—to show the final, client-facing price.
💡 Why this is important
Custom meters and flexible billing are powerful, but pricing must be consistent and whitelabeled. This API prevents accidental exposure of internal rates and ensures the sub-account only sees the final price they intend—across Marketplace and custom experiences built by app developers.
new
App Marketplace
API
Webhook Logs Dashboard in Developer Portal
🧭 Overview
We’ve added a Webhook Logs dashboard in the Developer Portal (Insights → Logs) to make debugging webhook issues fast, transparent, and self-serve.
Until now, developers and support teams had to file support tickets just to confirm if HighLevel had delivered a webhook — and we often discovered the issue wasn’t on HighLevel's end.
This new dashboard gives developers full visibility into webhook deliveries, retries, and responses — no support ticket needed.
✨ What’s new?
- New “Webhook Logs” tab under Developer Portal → Insights → Logs
- Developer experience optimised for debugging: Search by any substring in payload
- 30-day retention window
- Detail Panel: click any event row to view: Webhook ID, Attempt #, Event Name, Timestamps, Full Payload (with “Copy” button)
- Timezone-aware views — defaults to Central Time, overrides saved for future sessions
💻 How to use it as a Developer
- Go to Developer Portal → Insights → Logs → Webhook Logs
- Filter or search by webhook ID, event type, or timestamp
- Click any row to open the detail panel and inspect payloads, response statuses, and retry history
- Copy payloads easily for debugging
- Adjust timezone once — it’ll be remembered for future visits
💡 Why this is important
This feature puts webhook visibility directly into developers’ hands — reducing support tickets, accelerating issue resolution, and increasing trust in HighLevel’s delivery infrastructure.
Preview Images:
new
Conversation AI
Conversation AI - Auto Followup Enhancement
What’s New — Smarter & Context-Aware Auto Follow-Up for Conversation AI
We’ve rolled out a major enhancement to the
Auto Follow-Up
feature in Conversation AI! Previously, bots would sometimes send
unnecessary or excessive follow-ups
, even after a conversation had clearly ended — for example, when a user was disqualified, not interested, or had already booked an appointment. With this update, the bot is now
context-aware
and intelligently analyzes the entire conversation
— including the last few messages — before deciding whether to send or cancel a scheduled follow-up. This makes the bot more human-like, relevant, and respectful of user intent.
---
💡 How It Works
- No additional setup is required— simplyenable Auto Follow-Up, and this enhancement will workby defaultfor all your bots.
- The AI now evaluates the conversation’s tone, intent, and contextbefore executing a follow-up.
- Using agentic detection, it determines whether the conversation is still open or has ended.
- If the user no longer requires assistance, the bot will cancel the scheduled follow-up automatically.
---
When the Bot Won’t Follow Up
Here are scenarios where the bot will now
skip follow-ups intelligently
:- When the user is disqualified
Example responses:
- “Sorry, you’re not in our service area.”
- “We don’t provide that service in your location.”
- When the user expresses disinterest
Example responses:
- “Not interested.”
- No thanks.”
- “I don’t need your service.”
- When the user declines to book an appointment
- Example: “I don’t want to book an appointment.”
- If the bot ends the conversation, no follow-up will be triggered.
- If the bot continues the conversation, it will reassessif a follow-up is still necessary.
- When the user expresses anger or frustration
Example responses:
- “Leave me alone.”
- “Stop texting me.”
- “This is spam.”
- “Not looking right now.”
- When the conversation ends naturally or softly
Example responses:
- “Got it, Ryan. If you need anything else, feel free to ask.”
- “Thanks for the chat. Talk soon!”
- “That covers everything from my side.”
- “Hope that helps! Always here if you need anything.”
- hese indicate closure and no further follow-up is needed unless the user re-engages.
---
#Why It Matters
- Prevents unnecessary follow-upsthat may frustrate leads.
- Makes AI smarter and more naturalin understanding conversations.
- Maintains a professional and non-intrusivebrand experience.
- Saves time by automating context detectionfor follow-up logic.
new
E-Commerce Stores
Featured Product Element for Ecommerce Stores
What’s New?
We’re excited to introduce the
Featured Product Element
, a new drag-and-drop component that allows store owners to showcase individual product details anywhere on their store or website pages. Store owners can display any product with complete details (images, variants, price, description, and CTAs) on any store or website page.Key Highlights:
- Add the element from the Add elementsection in the Builder.
- Assign any product directly within the settings panel.
- Customize typography, colors, layout styling, aligning media (Left/Right).
- Toggle visibility for “Add to Cart”, “Buy Now”, Description, Reviews & ratings and Related Products.
How to Use It?
- Drag the Featured Product elementonto any page.
- Assign a product in the settings panel.
- Customize layout and text options.
- Save and publish your page.
Important Notes:
- Featured Product customizations are mutually exclusivefrom Default PDP and Custom PDP. It works independently, changes here won’t affect other product detail pages.
- It supports only one static product— not a collection or dynamic list.
- For navigation or CTA redirections, you can link directly to the Featured Productpage or use awebsite URL redirectby entering the preview URL.
Images:
new
improved
Blogs
Funnels and Websites
E-Commerce Stores
Improved Undo/Redo Experience in Page Builder
Overview
We’ve revamped the Undo/Redo system in the Page Builder to make editing smoother, more reliable, and faster. Every change is now tracked accurately across main pages and popups while using fewer system resources.
✨ What’s New and Improved
- Comprehensive Change Tracking:Undo/Redo now works across the entire builder including main pages, popups, and global settings like typography and tracking codes.
- Smart Popup Visibility:When undoing or redoing a change related to a popup, the builder automatically opens that popup so you can instantly see your edits in context.
- Optimized Performance:Improved snapshot logic uses less memory and makes editing faster and lighter.
- Better Text Editing:Text changes are now grouped together intelligently, so undoing doesn’t happen with every keystroke making it cleaner and easier to control.
🎯 Why This Matters
- Makes editing faster and smoother, even for complex pages.
- Reduces lag and improves reliability when switching between elements.
- Helps you edit with confidence, knowing every change is accurately tracked.
What’s New?
Businesses can now offer customers the option to add tips during checkout, enabling a more flexible and personalized payment experience across various product types.
This is majorly an API enhancement support for any checkout to implement tipping on their end and make it available on their checkouts. More settings related to tipping and an option to view and collect tips directly on the payment element will be available in the next phase.
With this update, tipping is now supported in the Payment Summary API and across all related order and transaction layers — ensuring accurate total calculations and transparent reporting.
Key Highlights
Comprehensive API Enhancement:
- The Payment Summary API now includes tipping as an optional input field.
- API calculations automatically include the tip in the total payment due.
- Error handling ensures invalid or missing tip values are flagged gracefully.
UI Enhancements for Transparency:
- Tip amount (if applicable on the checkout and enabled by the checkout) now appears in Transaction Details, Order Details, and Receipts.
- For Invoices, existing tipping behavior is retained — if the tip amount is greater than 0, it is displayed; if 0, it remains hidden.
CSV Exports:
- A new “Tip Amount” column (if applicable on the checkout and enabled by the checkout) is added to Orders CSV, showing the tip paid at order placement.
- Transactions CSV uses the existing tipping field for consistent reporting.
Where Can I Find This?
- Tipping support is available on the Payment Summary API and can be used by any internal team to pass their tip values/amounts to order totals.
What’s Next?
- Support for custom tipping configurations (such as predefined tip percentages) on Payment Settings.
- Collection of tip directly from the payment element.
- Extended analytics dashboards to visualize tipping adoption and value contribution.
- Broader UI customization support for how and where tipping is displayed during checkout.
Visual
Load More
→