Need more triggers & actions for Custom Objects
in progress
J
Joseph LaMothe
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.
Log In
S
Sarah Edwards
There are no triggers for important lifecycle events such as:
When a contact is associated with an object
When an association is created or removed
Filtering or triggering workflows based on association labels
Workflow actions for custom objects are also limited. There is currently no ability to:
Automatically change a contact’s association label based on conditions
Manage or update associations dynamically within workflows
Apply logic across multiple associated records
Impact:
This significantly limits automation for systems that rely on relationships between contacts and associated records, requiring manual intervention for association management and reducing the usefulness of custom objects in real-world workflows.
J
Julius Wiedemann
Needed. Date field trigger + communication actions are my top picks
Y
Yohani Rodriguez
There are two key improvements needed to unlock full workflow automation for Custom Objects:
- Full Workflow Support for Custom Object Triggers
Custom Object triggers (Record Created / Updated) should support the entire action set, specifically:
Send Document & Contract
Webhooks
Branching logic
Communication actions
Right now these triggers are restricted, preventing CO-based automation flows from functioning end-to-end.
- Custom Object Record as Document Context
Document Templates should support Custom Object Records as the primary context, allowing:
Dynamic population of Custom Fields
Selecting the associated Contact automatically
Sending the generated document directly within a workflow
Even though templates allow inserting CO fields, values remain empty because the workflow cannot assign a CO record as the active context.
Impact:
Enabling these two upgrades would allow proposals, contracts, project documents, and reports to be automatically generated from Custom Object data — a major step for advanced CRM implementations.
V
Victor Oben
Please add internal notification actions. As well as task creation action to custom object workflow.
A
Alexis Counts
If/ Else for all objects sent to the workflow via webhook
L
Lourens Swart
I seet his is in progress. Would be great if we can have a date trigger as well
P
Pallavi Kothari
marked this post as
in progress