Custom Objects

ability to use my custom object fields in emails - We want to use custom objects to be able to send our customers updates on their website projects. Right now if 1 client has multiple websites with us, we can't easily send them updates for each website. A custom object could be the perfect solution if we were able to utilize variables and triggers.

It would be great if pages & funnels could access Custom Objects and display them on the page, probably as a gallery. In our case, we're going to be showing properties. We'll have a featured image that we'd want to be displayed in a gallery, with some basic information from the custom object. Then the user can click that item to see the full details about that custom object (property).

Add the option to asossiate custom object automaticaclly in workflow. Right now i can just create one or update one but not asosiate one to another.

This trigger should activate when a Contact is associated with a Custom Object (or vice versa). Purpose: To enable workflows that respond immediately when an association is made between a Contact and/or Custom Object. Once triggered, the workflow should have access to the Contact and/or Custom Object data, allowing for dynamic and data-driven actions within the flow.

Formula Fields are very useful at extending capabilities and allowing users to quickly create automatic calculations rather than manually entering results. A formula field is a custom field that automatically calculates values based on a formula expression. Formula fields are read-only, meaning users can't directly edit the value. Instead, the value is calculated based on the formula and the values in the source fields. This is not a new concept, since most CRM systems such as Salesforce, Zoho, Hubspot, freshworks, vtiger, salesloft, MS Dynamics, and Sugar all have the ability to create formula fields. If you are familiar with Excel, than you know how handy formula fields are as they allow us to create simple or even more complex formulas based on data from a record and from its related records if needed. Some examples of use cases that come to mind are: Dynamic Payment Calculations for Appointments or Services For example, if each appointment hour costs $150 Formula: ( {{appointment.only_end_time}} - {{appointment.only_start_time}} ) * 150 Lead scoring based on Engagement and Attribution Formula: IF( {{contact.attributionSource.utmSource}} = "google", 10, 5 ) + ( {{ contact.email _open_count}} * 2 ) Visualize Lead Temperature (using IMAGE and CASE) Formula: CASE( {{contact.rating}}, "Hot", IMAGE("/img/samples/light_Red_fire.gif", "Hot"), "Warm", IMAGE("/img/samples/light_Yellow.gif", "Warm"), "Cold", IMAGE("/img/samples/light_Blue_snowflake.gif", "Cold"), IMAGE("/img/samples/light_grey.gif", "No Rating")) Add 30 Days to an Enrollment Date Formula: ( {{contact.enrollment_date}} + 30 ) The ideal situation would be whenever your are creating a custom field and you choose the Formula Field Type, it would allow you to open a formula editor where you could construct the formula and insert other fields, operators, and functions. Here are some Operators that should be included: Math Operators (+, - , *, /, ^ ) Logic Operators ( =, <, >, <=, >=) Logic Functions ( AND, OR, IF, CASE, ISBLANK, ISNEW, NOT, IS) TEXT Functions ( FIND, CONTAINS, HYPERLINK, IMAGE, INCLUDES)

Currently there are only 2 triggers in High Level for custom object. When an Object is created and when an Object is changed. We need more triggers like when a contact is associated with an object (filter by association label). Also we could use more actions in workflows for custom object. Like being able to change a contact's association label automatically when they meet certain conditions.

Urgently needed feature to be able to specify custom fields as objects - both, standard objects and custom objects.

In the current GHL workflow system, automations can create and manipulate custom objects as long as they are associated with a Contact. This is a great foundation — and we understand that the workflow must run on the Contact record. However, in many advanced use cases, multiple different custom objects are associated with the same Contact and also maintain a hierarchical relationship between them (many-to-one). Currently, there is no automation action that allows associating these objects with each other, even if they all share the same Contact and have a shared field that could be used to match them. Example Use Case (Travel Agency): • A Contact (client) is associated with a Closed Deal object. • The same Contact is also associated with multiple Flight and Hotel objects, each representing part of the trip. • Each Flight and Hotel belongs to the same Closed Deal (e.g., via a shared identifier or date range). • However, we cannot automatically associate the Flights and Hotels to the relevant Closed Deal in the CRM. This forces us to manually go into each Flight/Hotel record and link it to the appropriate Closed Deal — even though the data clearly shows they belong together. --- Suggested Feature: Introduce a new workflow action that allows associating related custom object records based on shared Contact and matching field values (e.g., match all Flights with Deal ID X to Deal X). This will: • Save hours of manual work. • Maintain clean and scalable data structures. • Unlock more complex automation logic based on real business models. I believe this addition would empower countless use cases across industries — including travel, real estate, education, and project management — where multiple object types need to be associated beyond just Contact relationships. Thanks for considering!

Hey team 👋 First of all — Custom Objects + Associations are a game-changer. They unlock a deeper CRM that goes beyond “single contact per record.” I love using associations to support real-world relationships like: Husband ↔ Wife Parent ↔ Child Member ↔ Coach Resident ↔ Carer Student ↔ Teacher This gives huge value to verticals like dance studios, gyms, schools, childcare, aged care, and medical practices where contacts naturally exist in relationship groups. 🚨 But the 1,000 association limit is a major blocker In the current setup, a standard family structure quickly consumes these associations: Example: Parent ↔ Child 2 parents + 1 child = 2 associations 2 parents + 2 kids = 4 associations 2 parents + 3 kids = 6 associations That means: Family size Associations used Business hits limit at… 1 child 2 500 families 2 children 4 250 families 3 children 6 166 families For many of my clients, 250–600 family relationships is TINY. A busy dance school or gym easily handles 1,500–4,000 family/member relationships. 🏁 Result: We can’t confidently sell this feature Ethically, I must tell customers upfront about the cap. But doing so kills confidence and potentially drives them to other CRMs that support scalable relationship mapping. GHL’s own documentation states: “The association limit is set to prevent performance issues and can’t be changed.” I totally understand the intent — performance matters. But as it stands, the limit forces us to cap who we can sell GHL to. This is business-limiting for us and for you. ✅ Proposal Please raise the association limit to something practical: ➡️ Minimum viable expansion: 20,000 associations per sub-account This would allow: Larger revenue-generating studios and gyms Multi-branch operators Verticals with natural multi-contact households More impactful automation and personalization Even better: ✔ Tiered limits based on plan level ✔ Ability to request increase via support ✔ Optimizations that allow scaling without performance issues 💡 Why this matters for GHL long-term Drives more mid-market adoption Makes GHL truly competitive with vertical CRMs Unlocks more automation and AI use cases Prevents need for external databases/workarounds Increases customer retention (ours & yours) ❤️ In short You built an AMAZING feature — but the current limit makes it impossible to deploy at scale in the industries that need it most. Please consider raising (or allowing paid expansion of) association limits so GHL can continue to scale with real-world business needs. Thanks for considering this — happy to provide further examples or testing support. 🙏