HighLevel Adds Association Created Trigger to Workflows
TL;DR
HighLevel introduced an Association Created workflow trigger in Labs to run automations when CRM records are linked.

TL;DR
HighLevel added an Association Created trigger to start workflows when CRM records are linked. It is currently in Labs.
Who this affects
HighLevel has not confirmed which plans or sub-accounts have access to this update, or whether plan gating applies. Anyone managing record relationships across Contacts, Opportunities, Companies, or Custom Objects should check Labs to see if it is active.
What changed
- Added an Association Created trigger in workflows, currently available in Labs.
- Supported record types include Contacts, Opportunities, Custom Objects, and Companies.
- Usable across standard workflows, Custom Object workflows, and Company workflows.
- Includes filter settings for associated object types and specific association labels.
- HighLevel has not confirmed whether this replaces or breaks any existing workflow functionality, nor have they published specific plan limits or rollout timelines.
Where to find it
Go to Automation > Workflows. Because this feature is currently in Labs, you will need to check your Labs settings to enable it. Once active, create or open a standard workflow, Custom Object workflow, or Company workflow, and select Association Created as the trigger.
How agencies will use this
When a user associates a Contact with a Company or links an Opportunity to a Custom Object, the workflow fires immediately upon creation of that link. You set the trigger filters so it only runs when a specific associated object or association label is detected. From there, the workflow can proceed with automated tasks for that linked record without requiring manual intervention.
Our take
This is marked as a major update, though HighLevel has not detailed the specific reason for that classification. If your agency actively links Contacts, Companies, Opportunities, and Custom Objects, having an automated trigger off that exact event saves time. Because it is still sitting in Labs, treat it as experimental and verify your association label filters before putting it into critical client setups.
Source: Official HighLevel announcement


