"Last modified date" as trigger for re-enrollment?

[LauraYepes]

I’ve tested the “Last modified date” for companies as a trigger within a workflow and enabled the re-enrollment option so after any update on the company, some other properties are updated too.

Seems like the re-enrollment is not working as expected… Do you know what other property I can use to achieve that purpose?

[LauraYepes]

The re-enrollment works when I turn off the workflow and then activate it again, but it’s not working automatically as it’s expected. Do you know if currently HubSpot is experiencing issues with this?

[karstenkoehler]

Hi @LauraYepes,

If you want the workflow to trigger whenever Last modified date changes, you should change the enrollment criterion to “Last modified date is known” and enable re-enrollment for it. HubSpot interprets “is known” as “has changed”, too.

Hope this helps!

[LauraYepes]

Hey @karstenkoehler

Thanks for your early reply. However, setting up as “known” is not working in this case. That option is not taken into account for the re-enrollment

Do you have any other ideas maybe?

Thanks!

[karstenkoehler]

Hi @LauraYepes,

You’re right, I had forgotten about this. This is probably to prevent loops in workflows. For this particular property, I don’t see a solution then.

If your main goal is to push certain fields, have you considered simply listing these fields in the enrollment criteria? Why trigger the workflow for any change when you can be more selective and only trigger it when one of the properties is changed that you actually want to sync/copy?

Best regards

[gcollette]

It’s not exactly the same as “known”, but you can use is “Last modified date” as a re-enrollment trigger if you use the “updated in last” option and set it to “1 day”.