How to avoid Butler rule from executing on cards that are emailed in?

[Olivia Henao]

Hello, 

I currently have a Butler rule to do the following that saves us all a couple steps when we set up cards:

when a card is added to the board by anyone, add member @{username} to the card, and set custom field "Owner" to "{creatorfullname}"

But we are about to start using the email-to-card feature for requests that we receive through an internal form. Since there is no generic "board" or team email, we'll use mine; the result is that all the cards that get emailed in end up with me automatically added to the card and custom field.

Is there any way I can prevent my rule from executing on cards that are emailed in?

Thanks!

[Hannah Humbert - Simpla Workflows · Accepted solution]

Hi @Olivia Henao ! You could make your trigger conditional so it doesn't apply to all cards on the board. One idea is to create a list called "New Requests" and have all cards that come from email default to that list. For your trigger, it could say "when a card not in list "New Requests" is added to the board".

[Olivia Henao]

That's exactly the list we're using for the requests, so this is perfect, thank you! I didn't realize there was a "Not in" option for that trigger. :)

[Olivia Henao]

Well I've found a "solution" since posting, which is to roll "remove all members" and "clear [Owner]" into another Butler rule I made specifically for emailed cards. It works, but it's not exactly what I'd call efficient haha, so I'll just keep this open if anyone has alternate ideas. :)