Custom Objects

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.

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.

At minimum, role permissions so certain objects can be restricted to admin. Ideally, user permissions to control object visibility by user.

Ability to be able to update fields in list view like a spreadsheet

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)

### The Problem When creating a Custom Object record, the creation form only supports basic field types: Text, Number, Date, Dropdown, Checkbox, Email, Phone. Contact associations (linking to an existing contact) only appear AFTER the record is saved — on the record detail page as a separate section. This forces users into a frustrating 2-step process: Step 1 → Create the Custom Object record (type a generic text name) Step 2 → Open the saved record → go to Associations section → search and link the contact --- ### Real-World Use Case: Referral Tracking I built a Referral tracking system using a Custom Object with these fields: Referred Contact (should be a contact picker) Referral Date Status (Pending / Converted / Lost) Referral Source The goal: Open a contact's page → see who they referred → click the referred person's name → open their contact record. Exactly like Salesforce's Related List + Lookup Field behavior. But right now, the only option for linking a contact is a TEXT field (not searchable, not clickable) or a post-save association (2-step, poor UX). --- ### Expected Behavior When building a Custom Object schema in Settings → Objects, add a new field type: "Contact" or "Contact Lookup" or "Contact Picker" This field should: → Allow searching existing contacts by name or email during record creation → Store the Contact ID (not free text) → Render as a clickable link on the record detail page → Be usable as a column in SmartLists / reports Optional: Allow this "Contact" field type to be set as the Primary Display Property of the Custom Object record --- ### What This Unlocks ✅ Referral tracking (Referrer → Referred Contact — both clickable) ✅ Borrower-to-Guarantor relationships ✅ Agent-to-Client linking ✅ Any many-to-one or one-to-one contact relationship stored inside a Custom Object ✅ Full parity with Salesforce Lookup Fields on Custom Objects ✅ Clean monthly/yearly reporting with contact-level detail --- ### Current Workaround (and why it falls short) Workaround A: Contact-to-Contact Association → Allows 1-step contact search ✅ → But no metadata visible in the related list (no date, no status) ❌ → All contacts look the same — no visual distinction ❌ Workaround B: Custom Object + Text Field → Salesforce-like display with date + status ✅ → But no contact search in creation — just free text ❌ → Name is not clickable ❌ Neither workaround fully solves the use case. A native Contact Picker field type in Custom Objects would close this gap completely. --- ### Priority / Impact This would directly benefit: Mortgage / Finance businesses tracking referrals Real estate teams managing agent-client relationships Any business migrating from Salesforce expecting lookup field behavior All power users building relational data models with Custom Objects

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.

If you are not familiar with the term Kanban, it is the setup we have for Opportunities. View picture. Add custom statuses like we have in Opportunities for Stages to the Kanban view.