# Triggering a workflow based on any property change

**URL:** <https://community.hubspot.com/t/triggering-a-workflow-based-on-any-property-change/68148>\
**Category:** Lists, Lead Scoring & Workflows\
**Tags:** free, professional\
**Created:** [October 28, 2022, 6:52pm UTC](https://community.hubspot.com/t/triggering-a-workflow-based-on-any-property-change/68148 "2022-10-28T18:52:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![RushiJoshi](https://avatars.discourse-cdn.com/v4/letter/r/ba9def/32.png) [@RushiJoshi](https://community.hubspot.com/u/RushiJoshi)\
**Post date:** [October 28, 2022, 6:52pm UTC](https://community.hubspot.com/t/triggering-a-workflow-based-on-any-property-change/68148/1 "2022-10-28T18:52:43Z")

</div>

Hi,

We are integrating hubspot with an internal tool, for this we need to trigger a workflow everytime any (one of the 30 or so) properties on a deal changes.

Ideally we want one trigger that will occur if any property on a deal is updated. Currently we are using the property → isknown condition with 30 or blocks.

I came across this post [Solved: HubSpot Community - Trigger to detect changes in any Company Property - HubSpot Community](https://community.hubspot.com/t5/Lists-Lead-Scoring-Workflows/Trigger-to-detect-changes-in-any-Company-Property/m-p/623552) but this seems to not work any more as LastModifiedDate is not allowed for re-enrollment.

Any help on this would be hugely appreciated.

Thanks!

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [October 28, 2022, 9:39pm UTC](https://community.hubspot.com/t/triggering-a-workflow-based-on-any-property-change/68148/2 "2022-10-28T21:39:23Z")

</div>

Hey, @RushiJoshi 👋 I moved this one over to the Workflow-specific area. Hopefully, we’ll get some eyes on it over here 😊  
If you have an additional question relating to API use or webhooks, for example, please update this post or create an additional one.

Best,

Jaycee

---

<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:** [October 29, 2022, 7:28am UTC](https://community.hubspot.com/t/triggering-a-workflow-based-on-any-property-change/68148/3 "2022-10-29T07:28:50Z")

</div>

Hi @RushiJoshi,

Setting up the re-enrolment with those 30 criteria, as dumb as it may seem, would be the most reliable workaround / solution.

What purpose does this workflow have?

Best regards!

---

<div class="post-metadata">

**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:25pm UTC](https://community.hubspot.com/t/triggering-a-workflow-based-on-any-property-change/68148/4 "2023-11-08T13:25:57Z")

</div>

> * * *
> 
> Currently we are using the property → isknown condition with 30 or blocks.

Wouldn’t that be 60 blocks? Because “is known” would not trigger if the property has been emptied. You want to include both scenarios “is known” or “is unknown”.  
It would be nice to have an actual “has changed” option in the event based triggers, with a multiselect of fields. Like “any of these fields … have changed”.