I
Ido Havazelet
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!

Photo Viewer

View photos in a modal