We populate custom date fields through API integration and use them to write automation/triggers. The possibility to write conditions using "is within the next/previous" number of days has been very helpful, but it falls short when it's not possible to write the opposite rule (i.e. "is NOT within the next/previous" number of days).
Since for all other conditions it is possible to write rules both ways (e.g. "is" and "is not") it feels natural the same should be possible when it comes to date fields.
Here is one example:
We have one user parameter called <published_at> that populates with the date of the user's latest published listing on our marketplace. We then have the following trigger:
IF <published_at> is within past 3 days THEN add tag "make onboarding call" to associated ticket
We can then view all onboarding tickets in a view. However, we want to remove the tag "make onboarding call" once the <published_at> parameter gets old. To do this we would need a way to write an inversed condition (e.g. "is NOT within the past 3 days" or "is older than 3 days").
How can we make this happen?
Please sign in to leave a comment.