# Workflow Trigger On Value Change **URL:** \ **Category:** CRM\ **Tags:** workflows\ **Created:** [February 23, 2023, 1:47pm UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845 "2023-02-23T13:47:51Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Mark\_T](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mark_t/32/193320_2.png) [@Mark\_T](https://community.hubspot.com/u/Mark_T)\ **Post date:** [February 23, 2023, 1:47pm UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/1 "2023-02-23T13:47:51Z")
So, I’d like to make a suggestion for an improvement to workflows, please. Currently, we have a deal-based workflow that gets triggered if a property has been updated within the last 24 hours. However, when this happens, the workflow only triggers once in that 24 hour period. So, what I’d like to see is a trigger condition of “Whenever property \ changes”, irrespective of time period. We have an integration to an external system that runs twice daily and as a result of this, the workflow can only run once against the deal, even if there’s been two property value changes. ---
**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\ **Post date:** [February 23, 2023, 1:50pm UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/2 "2023-02-23T13:50:08Z")
Hi [@Mark\_T](https://community.hubspot.com/t5/user/viewprofilepage/user-id/326113), You can achieve this by adding a trigger filtering for “[property] is known”. Whenever the value changes, HubSpot will recognize that change through this trigger. E.g. if you want to trigger workflow enrollment when a deal name changes, set it to “Deal name is known” and enable re-enrollment for it. Best regards ---
**Author:** ![DavidVoigt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/davidvoigt/32/47231_2.png) [@DavidVoigt](https://community.hubspot.com/u/DavidVoigt)\ **Post date:** [November 8, 2023, 1:29pm UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/3 "2023-11-08T13:29:27Z")
\> if you want to trigger workflow enrollment when a deal name changes, set it to “Deal name is known” and enable re-enrollment for it. This will only work if the new property value is “known”, i.e. not empty. You would have to account for an emptied field with a new trigger group. XYZ is known OR XYZ is unkown ---
**Author:** ![Mark\_T](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mark_t/32/193320_2.png) [@Mark\_T](https://community.hubspot.com/u/Mark_T)\ **Post date:** [February 23, 2023, 2:32pm UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/4 "2023-02-23T14:32:57Z")
But won’t a property be “known” just once? So, if Property X was empty and then has “1” in it, the workflow would trigger, because it is now known. If Property X was “1” and becomes “2”, it wouldn’t? If this is indeed the case, that’s contrary to the HubSpot advice I received, saying that there was no workaround for this. Many thanks, Mark. ---
**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\ **Post date:** [February 23, 2023, 2:34pm UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/5 "2023-02-23T14:34:50Z")
Hi [@Mark\_T](https://community.hubspot.com/t5/user/viewprofilepage/user-id/326113), > * * * > > [@Mark\_T](https://community.hubspot.com/t5/user/viewprofilepage/user-id/326113) wrote: > > If Property X was “1” and becomes “2”, it wouldn’t? Yes, it would, as long as re-enrollment is enabled for this trigger. I’d recommend testing this yourself so you can see it in action. Best regards ---
**Author:** ![Mark\_T](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mark_t/32/193320_2.png) [@Mark\_T](https://community.hubspot.com/u/Mark_T)\ **Post date:** [February 27, 2023, 10:10am UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/6 "2023-02-27T10:10:24Z")
Hi, I gave this a try. As suspected, it only triggers once, not on subsequent changes. Reenrollent is enabled, as suggested. To reiterate, I need the workflow to trigger each time there’s a change to the property value. ---
**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\ **Post date:** [February 27, 2023, 10:11am UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/7 "2023-02-27T10:11:40Z")
Hi [@Mark\_T](https://community.hubspot.com/t5/user/viewprofilepage/user-id/326113), Can you please share a screenshot of your enrollment criteria and your re-enrollment settings? What exactly was your test setup? Best regards ---
**Author:** ![WimbaRF](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/wimbarf/32/14088_2.png) [@WimbaRF](https://community.hubspot.com/u/WimbaRF)\ **Post date:** [May 15, 2024, 11:06am UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/8 "2024-05-15T11:06:30Z")
I am experiencing the same problem on company bases: re-enrollment doesn’t work when a company is associated with a deal and the deal changes its stage. Also, workaround is on the “black list” as " **The following enrollment conditions can’t be used for re-enrollment"** ![WimbaRF_0-1715771039865.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/f/3/f3fdb04e7c0f2524fbcc1aa4b166f9e4d8806adf.png) ---
**Author:** ![annecaylin](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/annecaylin/32/202410_2.png) [@annecaylin](https://community.hubspot.com/u/annecaylin)\ **Post date:** [September 26, 2024, 3:33pm UTC](https://community.hubspot.com/t/workflow-trigger-on-value-change/75845/9 "2024-09-26T15:33:49Z")
I’m experiencing the same thing. Any luck?