Greater Than or Less Than contingencies in Automations
Ray Aguirre
For Custom Fields, the current options for contingencies only include "is equal to", "not equal to", "is set, and "is not set." It would be great if Automations could also make changes based on "less than" or "greater than" contingencies.
Log In
Gia Ciccone
Agree. Example of what I would love (if it's helpful to team CU) -
If a "Money $" custom field has an input value over $100,000, it would trigger a comment tagging our VP requesting their approval.
Steph
yes that would be great i have affiliate clicks and sales of my affiliates in custom fields and to create nice activity flow based on their performance i can move them through different stages, what is not possible with just a number lets say for example 100 clicks what happens if the affiliate has 99 or 100 clicks, so this would be really great
Lauren Petrullo
our subtasks are dependent on the domain authority's number. Without having this contingency I'm not able to automate anything for off page SEO work