I’m wondering if it’s possible to trigger a workflow when a property on a Custom Object is changed?
The bigger picture is;
We have a “License” custom object in Hubspot and an identical record in another system (NetSuite). We want to make sure that updating the License object in Hubspot will also update the record in NetSuite.
So ideally, ANY change to the Custom Object would trigger a workflow- which we can then use Custom Code to send the data to NetSuite to be updated.
The latter part, I have working- I just can’t figure out how to start the workflow when a property on the Custom Object is changed.
@EBirdsall Hi there 
Thanks for your question. My name is Olivia and I am happy to help! Here are the steps you need to follow:
1) Go to workflows and create a worfklow
2) Create a custom-object based workflow. If you scroll down on on the list of possible wrkflow types you should find the option of ‘name of your object- based workflow’.
3) As the trigger, choose the property you want to use to trigger the workfow and select ‘is known’. Then save this selection.
4) Next, select the enrollment trigger box again and go to the ‘re-enrollment tab’. Turn on re-enrollment for when the chosen property is known. This will ensure the workflow triggers everytime the value of that property changes.
I hope this helps!!!
Here is a quick video for reference too: New Recording - 24/10/2022, 12:49:59.
If this solution helps you, please mark it as solved
Hey Olivia, thanks for the reply and the video! It looks like there is a limitation on my “dream scenario” of easily triggering a workflow when any field changes; If I set the field to “Object last modified date/time”, and try to use it for Re-enrollement, Hubspot says that I can’t use this field
I was hoping I’d just be able to use that field to catch all changes- but it looks like I’d need to add each field of the Custom Object to the workflow one at a time… and with 122 fields on that Custom Object, I don’t know if this is the route we want to take.
Alas, I’ll continue to try to find a work-around. But for anyone reading this- the solution provided is 100% accurate, it’s just that my particular case doesn’t appear to be supported by Hubspot.
Thanks again!