I'm working with a client who wants to build out an ongoing workflow to edit Lifecycle Stage based on changes to the contact's lead score. I've got the workflow built out, branching based on greater than/equal to values per lifecycle stage.
Enrollment trigger is "Property value changed," property is HubSpot Score, new value = known.
My question is, if I want to make sure the workflow is running in the background and enrolling/re-enrolling contacts whenever their score changes should I set the new value criteria in the trigger to "known," or "greater than 0?"
If you want this to apply to existing records, I'd recommend changing the trigger criteria to "When filter criteria is met" > "Score is known", and then enable re-enrollment. This is interpreted by HubSpot as a "enroll records whenever the value changes".
Event-based triggers only apply when the workflow is running.
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
If you want this to apply to existing records, I'd recommend changing the trigger criteria to "When filter criteria is met" > "Score is known", and then enable re-enrollment. This is interpreted by HubSpot as a "enroll records whenever the value changes".
Event-based triggers only apply when the workflow is running.
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer