Contact Added to / Removed from Smartlist Workflow Trigger
J
Jared Gobler
This is wayyyy overdo and has so many advantages to it that we cant do with the current workflow triggers.
Best example are using date fields so that when a date hits a certain range mixed with all the other tag and parameters it adds it to s Smartlist which then triggers the automation.
Smartlist are dynamic which make them as powerful as they are, and would allow for less contacts to be stuck in a workflow for long periods of waiting times and can be added when they hit the criteria f the smartlist to be added and then put into the work flow
The list goes on and on with what this could do for automation purposes and workflows etc.
Log In
K
Keith Besherse
Jared Gobler, I think you haven't thought through how this would work.
There are date related filters that can be used to define a SmartList. But, if the workflow trigger were (for example) February birthdays, how would the SmartList know that it is supposed to act on the February birthday SmartList. All of the Contacts are data-at-rest in the SmartList waiting to be acted on. The CRM isn't actively crawling the Contact database looking for data points. The way this operating system is structured is exactly the opposite. The Workflow automations define what action is to be done. The Contacts (and increasingly Opportunities and Objects) are what is acted upon. The SmartList doesn't initiate action (verb), it is the noun that has action done to it.
Unless I TOTALLY misunderstand what you are trying to describe...
K
Keith Besherse
The triggering action is whatever caused the Contact to be qualified for that SmartList (not the fact that it is now part of the filter set which defines that particular SmartList). So, when the date in question is changed to meet the SmartList criteria, that data change could be used as a Workflow Trigger event. But the Trigger is initiated by data change, not data-at-rest.