# Workflow entry & flow based on property value changes

**URL:** <https://community.hubspot.com/t/workflow-entry-flow-based-on-property-value-changes/128754>\
**Category:** Lists, Lead Scoring & Workflows\
**Tags:** workflows, best-practices\
**Created:** [March 27, 2025, 5:30am UTC](https://community.hubspot.com/t/workflow-entry-flow-based-on-property-value-changes/128754 "2025-03-27T05:30:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AdamDx](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/adamdx/32/38099_2.png) [@AdamDx](https://community.hubspot.com/u/AdamDx)\
**Post date:** [March 27, 2025, 5:30am UTC](https://community.hubspot.com/t/workflow-entry-flow-based-on-property-value-changes/128754/1 "2025-03-27T05:30:04Z")

</div>

Hey all!

Trying to wrap my head around how i would action this and while im not 100% certain i wanted to put the call out for input.

Context - i am trying to figure out a workflow entry based on a property/value change which would dictate/guide next steps.

for this example - the test property is “ **Tier** ” (loosely resembling a loyaliy tier setup) - this has the range of potential values of **Basic, Plus, Super &**  **Platnium**.

I’ve setup the workflow entry criteria with:

- **Tier** has been updated within the last **1** day

In this particular situation - most contacts would start on the **Basic** tier and then depending on their activity be transitioned to **Plus, Super or Platnium** depending on various factors.

After the entry criteria i have a branch setup which identifies and splits out the contacts based on their **Tier** such as **Basic, Plus, Super or Platnium** this all seems straight forward - Each of these branches have subsequent activities for action (emails, in product messages, other automations, etc) except for **Basic** where nothing will happen and they exit as intended.

With this setup - to me it would assume that anyone who has the value of **Tier** change within the last 1 day would enter the workflow as intended, however i feel like i am missing something - Is it as simple as that? **Or** should i be including an additional filter or requirement that (and im not entirely sure it was possible) the initial value of **Tier** = **Basic**.

Would love some input and thoughts.

Thanks!

---

<div class="post-metadata">

**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:** [March 27, 2025, 5:41am UTC](https://community.hubspot.com/t/workflow-entry-flow-based-on-property-value-changes/128754/2 "2025-03-27T05:41:24Z")

</div>

Hi @AdamDx,

If you filter for “last updated”, then multiple changes in value in that time frame would not trigger reenrollment (which you want). You would have to set it up as follows:

- Enrollment based on ‘When filter criteria is met’
- Specify ‘Tier is known’
- Enable reenrollment for this filter

HubSpot will now reenroll the record whenever the value in tier changes or when it is first known.

Best regards

---

<div class="post-metadata">

**Author:** ![AdamDx](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/adamdx/32/38099_2.png) [@AdamDx](https://community.hubspot.com/u/AdamDx)\
**Post date:** [March 27, 2025, 6:07am UTC](https://community.hubspot.com/t/workflow-entry-flow-based-on-property-value-changes/128754/3 "2025-03-27T06:07:57Z")

</div>

Hi @karstenkoehler

Thanks for the response - that makes sense including the “is known” filter variable.

The logic behind having a filter setup like this:

**Tier is known**

and

**Tier is not equal to any of Basic**

this would absolutely meet the criteria, however i did not factor it in for consideration as i’ve had some _interesting_ experiences in other MA platforms where we effectively created an infinite loop (enrolling the same set of contacts over and over, etc) due to the value being populated or “known”.

After reading this: [Add re-enrollment triggers to a workflow](https://knowledge.hubspot.com/workflows/add-re-enrollment-triggers-to-a-workflow#:~:text=When%20re%2Denrollment%20is%20enabled,re%2Denroll%20in%20two%20ways:) which explains that if the “value is known” it will trigger reenrollment when it is updated.

Thanks again @karstenkoehler - appreciate the help!

---

<div class="post-metadata">

**Author:** ![PamCotton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pamcotton/32/47916_2.png) [@PamCotton](https://community.hubspot.com/u/PamCotton)\
**Post date:** [March 27, 2025, 9:06pm UTC](https://community.hubspot.com/t/workflow-entry-flow-based-on-property-value-changes/128754/4 "2025-03-27T21:06:15Z")

</div>

Thank you for helping @karstenkoehler, and @AdamDx for sharing what you solved on your end.

Kindly,

Pam