There isn't an out of the box feature for this but with a custom property and an additional workflow, you can easily set up a workaround.
The idea here is that you always copy the value from the original property (1) into another property (2). By default, copying this value would take a few seconds. However, if we use a delay, there is always a window when the assisting property (2) still has the old value. You can then simply reference the discrepancy between old/new in your actual workflow.
See an example below. The second workflow would trigger if the original property (1) was changed from A to B.
Let me know if you have any questions on this!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
There isn't an out of the box feature for this but with a custom property and an additional workflow, you can easily set up a workaround.
The idea here is that you always copy the value from the original property (1) into another property (2). By default, copying this value would take a few seconds. However, if we use a delay, there is always a window when the assisting property (2) still has the old value. You can then simply reference the discrepancy between old/new in your actual workflow.
See an example below. The second workflow would trigger if the original property (1) was changed from A to B.
Let me know if you have any questions on this!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer