Changelog

🎉 What’s New?

You can now embed funnels into WordPress as Native HTML directly via the LeadConnector Plugin. This opens up powerful use cases previously restricted by iFrame limitations.

🚀 Key Features

• 💰 Unlock Payments via Order Forms:

  Previously, many customers faced issues using Order Forms within iFrame-embedded funnels, as certain payment gateways imposed security restrictions. With the Native HTML embed, these limitations are eliminated — enabling seamless payment collection directly on WordPress sites.

• 🧩 SEO Enhancements:

  Since the funnel content is now directly part of the page’s HTML, search engines can crawl and index it more effectively. This improves your website’s SEO visibility and discoverability.

🛠 How to Use

• Open the LeadConnector Plugin Dashboard in WordPress.

• Navigate to theFunnels tab.

• Click Add New Page (top right).

• Select the relevant Funnel and Step.

• Under Page Display Method, choose Native HTML Embed.

• Click Save Page to publish it.

🔧 Bug Fixes & Backend Improvements:

Fixed a minor UI bug where the Funnel ID was visible when adding or editing a funnel.

To know more about the WordPress Hosting, and how you can resell it to your clients, click here 👈

We’ve introduced key improvements to the Custom Webhook action, focusing on enhanced security for sensitive information. These updates aim to protect secret keys from being exposed in plain text and provide more streamlined credential management.

What’s New

Masked Secret Keys

Sensitive credentials (e.g., secret keys) are now stored securely and masked in the interface, preventing accidental exposure. This applies to Basic auth, Bearer token, and API key authentication methods.

User-Friendly Management

When updating or deleting existing keys, the interface guides you through the process without ever displaying the raw values, helping you avoid accidental leaks.

Why It Matters

Enhanced Security

• Reduces the risk of revealing sensitive information for data protection. Going forward, these keys would not be visible to the users in plain text format. These would be visible by the key name.

• These keys cannot be edited or deleted by users in a location. Only agency admins and users that have created these keys will have these permissions.

How to Get Started

Add a Custom Webhook Action

In your Automations builder, select Custom Webhook.

Select Authentication Type

• Choose Basic auth, Bearer token, or API key.

Configure Credentials

• Enter your secret key in the new masked field.

Monitor & Manage

• Use the dropdown menu to add or delete keys as needed.

Note

• Existing Keys: Any existing key will be deleted once a new key is updated.

• Deletion Permissions: Only agency admins or the user who originally created a key can delete it.

Context:

• A sizable number of marketplace app installs are done using the Marketplace OAuth link(example). These links are embedded in third-party products' integrations page that allows integration with HighLevel.

• This is similar to the Google OAuth link, where Google informs the user that an external site is about to access their account data and seeks your confirmation to proceed

• When users arrived on this site, until today, they weren't made aware of which permissions the app was getting access to from their accounts.

What's new?

• We have created a new OAuth page where we give users a heads-up about the app they're about to install and inform them about the permissions the app will have access to.

• If a private app attempts to access sensitive permissions, such as user.write, we explicitly warn the user.

• This feature is also available on the Marketplace's grey-labeled OAuth page(example)

Why is this important?

This feature provides sufficient details to users, allowing them to make informed decisions about the API access they're granting to third-party apps and thereby securing their accounts from unauthorised access.

Preview Images