Workflow Trigger if property has changed

HubSpot Ideas
1

A good option would be to be able to select in the trigger whether a property has changed and only then start the workflow. This means not at the first entry, but only from the second entry onward. In other words, the workflow should be triggered only when there is a change from the original value. For example, in the case of a changed contract start date (date property), a task should be created, but only in this case.

2

Supporting this proposition!
I don’t know what value the property will be changed to so the options available today (property value is “…” or a formula don’t suit me - I just need to set up an action when someone edits the property - to anything

3

A workaround for this …

Create a custom number property to indicate how many times the Contract Start Date has been updated (“Contract Start Date Updated”).

Set the enrollment trigger to Contract Start Date is Known (which will trigger on first entry as well as every time it changes); turn on re-enrollment.

The first step would be to increase “Contract Start Date Updated” by 1.

Then, if/then branch to check if "Contract Start Date Updated " = 1 - no nothing.

If 2+, create task.

4

Thanks for this solution @jessicavs

The property is known/property is updated trigger on Workflows includes both the First Initial Set and also any updates

So if you are trying to have a workflow trigger only if a property is updated

Instead of when it was initially set

This is the best way

5

I absolutely support this idea. Our organisation needs a trigger for when a property is updated, not when the property is initially known, and allow re-enrolment. To get around this we have to set the trigger to ‘is known’ so that all records enroll. They then sit in a 1,825 day delay (the max allowed): Delay up to 1,825 days until one of the following happens: Property value changed. It’s frustrating that all records have to enrol in this just to be able to capture changes, there should be a much simpler way. I have read the above workaround which is also good but there should be an easier way.