Trigger Received At

I dream of the day when, instead of ALL/ANY sections, we can manage conditions with logical operators (like liquid markup).

condition 1

condition 2

condition 3

(1 AND 2) OR (2 AND 3)

Was provided with a work around from some of the moderators, but having the ability to exclude emails using "Received  AT is NOT " would have saved us so much time. Appreciate all you do, looking forward to seeing how ZD grows. 

Hello @Zendesk Team - do you happen to have an update on this one please? Can we possibly have this condition as it is very helpful.

Not sure why we only have Received at > is >.

Thanks! 

@chris142 Is there any update on this one? It's difficult to maintain triggers with several Meet ANY received at is conditions when you have several emails being managed in an instance.

Hi Everyone - 

New PM for Triggers & Automations here, catching up on the requests in the Community. It has been great to see all the feedback from you! I certainly understand your frustrations around inconsistent operators and needing more flexible logic to build your triggers. We are actively working towards improving these areas.  

As for the original ask in this post, adding 'is not' for the received at condition, I'm working with the engineers to understand the level of effort. It may take a little investigation work, but you can expect an update from me in the next few weeks. 

UPDATE:11/17/2022

We have opened an investigation task around adding 'is not' logic to the received at condition. I'll share more once that is complete. Thanks all!

+1

Absolutely need this!

+1

Hi everyone - Please see the latest announcement, the "is not" operator for "received at" is currently rolling out! 

Thanks again for all your feedback on this, we hope it helps with your workflows.