Filters / Triggers for Properties that have changed in a specific time period

[1jdolly]

Is there a way to create either:

1. A list of contacts where property is now A but was B in the last 90 days

2. Trigger a workflow based on contacts who became X from Y in the last 7 days

These are just examples. I know you can do triggers by properties that were updated to a property but I'm not seeing how to trigger based on the update from a specific property.

[karstenkoehler · Accepted solution]

Hi @1jdolly,

If you want to specifically refer to a property value, you need assisting workflows and custom date properties.

• Create a "Last A date" and "Last B date" date property
• Create a workflow that re-enrolls contacts when value = A, then uses 'Edit record' to set 'Last A date' to the current date
• Do the same for the B date

Once you have these date properties, you can use them in lists, e.g. value = A but 'Last B date is less than 90 days ago'.

Best regards!

[SealaB]

Hi @1jdolly, Welcome to HubSpot Community!

You’re right that HubSpot doesn’t have a native “became X from Y” operator that checks the immediate previous value of a property. But you can get fairly close using property criteria like:

• Property "is any of" A
• AND Property "has ever been" B
• Optionally refine with a date condition such as the property being updated in the last 90 days (where available).

This filter would sequester contacts that currently have value A, has held value B at some point historically, and that change happened recently. It is important that this does not strictly guarantee the path was “directly from B to A”.
 

Similarly, for a workflow enrollment trigger, you can use:

• Property "is any of" X
• AND Property "has ever been" Y
• AND Property "was updated in the last" 7 days, using the relative “updated in the last X days” operator (where supported).

Again, this will capture contacts who currently have X, previously had Y, and whose property changed within the last 7 days, but it won’t enforce that Y was the immediate previous value.

Looping in @karstenkoehler and @OPerek-Clark here as well as experts with these types of complex historical value triggers.
Hopefully they have some additional methods of achieving this that they can share with us!