Forms

Right now, we can do almost every file extension, but no videos. IMO we need this Use case: Video Review collecting.

Form templates are great for creating good looking forms quickly but you just want the styles, not all of the custom fields from the form template. It's a pain to have to go and delete all of the custom fields the normal user does not realise are being created when choosing a form template.

The Form builder needs some quality of life changes. Its so tidies to make forms without the ability to duplicate elements... Please add: ➕ Ability to duplicate text element ➕ Ability to duplicate image ➕ Ability to duplicate slides (survey) ➕ Select images from Media Storage ➕ Add global color picker (like funnels and websites) with brand colors

This should have way more attention on it! Multi-step forms have a great impact on marketing and conversion rates! Being a user and seeing a form that just asks name and email, then a "next" button is way more digestible and motivating to fill out than seeing one giant form with 50 questions. Aside from this, it would be amazing to store partial form fills (For example if someone comes to the form, fills out their name and email, then closes the window before they press "Submit" or "Next" then we record that in db. Another great feature would allow you to determine which are incomplete and which are complete in workflows so you can say: "Hi Name, I see you didn't finish filling out our form..." For that, I guess you can do an if/then logic to say if 1 thing is filled out, but not another, but that can be cumbersome if there are many questions on the form.

We need the ability to use custom fields from Custom Objects as merge tags across all communication and document tools within HighLevel. Current Limitation: Right now, merge tags are limited to standard objects (Contacts & Opportunities). Custom Object fields are not accessible when building: Email templates SMS messages Documents / contracts This creates a major gap when using Custom Objects as the primary data structure (which is increasingly the case for more advanced use cases). Requested Functionality: Allow users to: Select a Custom Object Access its associated fields Use those fields as merge tags in: Emails SMS Documents (contracts, proposals, etc.) Example Use Case: We use a Custom Object called “Properties” with fields like: Property Address County Acreage Purchase Price Legal Description We need to dynamically insert this data into: Offer emails to sellers SMS follow-ups referencing property details Purchase agreements and documents Expected Behavior: Merge tag picker should include Custom fields from Custom Objects. You are currently able to select the merge tag but the data doesn't transfer. Ability to reference: The associated Custom Object record tied to the Contact/Opportunity Specific fields within that object Ideally supports multiple object relationships (if applicable) Why This Matters: Custom Objects are becoming the backbone of more advanced workflows. Without merge tag support: Automation is limited Manual work increases Document generation becomes inefficient or impossible at scale This feature would unlock significantly more powerful use cases and make Custom Objects truly usable in production workflows. This is High Priority for any business using Custom Objects as core data structures

Have the hidden field supersede the requirement, but only if the field becomes unhidden, THEN make the completion of that form field be required.

Can we get a section in forms for internal notes and fields. Our practitioners need to add internal information to the forms that clients have filled in as part of the legal requirement. The output would reflect both sections - client and internal.

Currently, the standard form implementation on ghl sites and form embed (iframe) for external sites automatically loads tracking and session scripts (e.g., Facebook Pixel, Google Analytics, internal session tracking) — even when these are not configured or needed for the specific form. This causes a critical problem for users in the EU/EEA: Cookie consent tools (e.g., Cookiebot, Borlabs, Complianz) detect the third-party scripts inside the iframe and block the entire form — not just the scripts. For essential forms like contact forms, this means the form is completely invisible to visitors who haven't accepted tracking cookies. The current workaround is to build a custom HTML form and send data via Inbound Webhook, bypassing the embed entirely. This works, but it defeats the purpose of having a form builder. Proposed solution: Add a "GDPR Mode" or "Tracking-Free Embed" option in the form embed settings that: Strips all tracking/analytics scripts from the iframe Loads only the form markup, styles, and submission logic Keeps full functionality (field validation, submission to CRM, workflow triggers) This would make GHL forms usable out of the box for the entire European market without requiring custom development. Impact: Any GHL user serving EU-based clients or operating in the EU is currently forced to work around this limitation. A native solution would significantly reduce churn risk and support tickets related to forms "not showing up."

It would be super to have forms inside the system where admin could fill them out without having to keep up with links.

More customization regarding payments. I am a non-profit and some donors want to pick and amount, some want to do custom amount. Some want to cover processing fees. because you only allow one payment element this can't happen. Also, custom amount should just have an open box so they don't have to push another button.