Compare hubspot property before and after values in a workflow running currently

[PieterVHeerden]

Hello Community

We have a requirement to see the previous value when a property was changed. This change sparked a workflow to run as part of the re-enrollment triggers.

We dont want to loop through all the JSON paylod history, but we only want to see what was the value, and what is it now in the current workflow that triggered the event. 

Thanks

Thanks

[PieterVHeerden]

Maybe this will change things.....We don't use this in internal comms or anything. We want to at any given time just see what the current deal stage is....and compare it with the previous deal stage. So the pause would only help us if I wanted to email or do something with that field, but its to be able to look at the 2 fields at any given moment and see the difference. 

the very first time the WF runs, it would be the same value, but once a deal moved through the stages, the prvious stage roperty will always have the last value

• Deal Stage has value A
• Previous Deal Stage has value A due to the first time the WF ran and we copied it to Previous Deal Stage
• Deal Stage is changed to B
• Previous Deal Stage still has value A
• Deal Stage is changed to C
• Previous Deal Stage is changed to B

and so forth

[karstenkoehler]

@PieterVHeerden this is not possible with workflows at the moment.

Can you explain in a bit more detail why you want this information? Why not just look at the property history for the deal stage? https://knowledge.hubspot.com/records/view-record-property-history#view-historical-values-for-a-prop...

[PieterVHeerden]

Hi Karsten,

Thanks for reaching out.

I am not sure if this approach would work, but only the first time round.

What will happen when that same property changes again for a second time? your pause of 5 min wont work because the data would already have changed in the original property, meaning you would write the new value to the cloned property and not the old one.

Thanks

[karstenkoehler · Accepted solution]

@PieterVHeerden it would work – as long as changes happen after the delay has passed.

Here's an example:

• Property has value A
• Property is changed to B
• Property (previous value) still has value A (for as long as you set the delay)
• Internal notification will include Property = B and Property (previous value) = A
• After the delay, Property (previous value) will be set to B
• Property is changed to C
• Property (previous value) still has value B (for as long as you set the delay)
• Internal notification will include Property = C and Property (previous value) = B

Just make sure to set up re-enrollment for "Property is known" and this will work. If you don't believe it, just set it up and try it 😉

[PieterVHeerden]

100% let me try this out. Will be very happy if this works 🙂

[karstenkoehler]

Hi @PieterVHeerden,

Is the use case to include the previous value in an internal email notification?

If so, this can currently only be achieved with an assisting property and an assisting workflow. Let's assume that the name of your property is 'Property'.

1. Create a clone of 'Property' and call it 'Property (previous value)'
2. Create a workflow that re-enrolls records when 'Property is known'
3. Add a delay of 5 minutes
4. Copy the property value from 'Property' to 'Property (previous value)'
5. Use 'Property (previous value)' in your internal notification

Due to the delay, for five minutes the new property will always contain the previous value.

Best regards