Hello @suuriyas ,
You can try using the default condition builder for this. In there, use the User or User ID field (since it's a reference field), and dot-walk further to the user's email. Once you have the email field, you can set the condition to check if it ends with @tesla.com or @ford.com.
Also, I noticed in my instance that if the sender isn’t present in the User table, the User field gets set directly as a string. In that case, you can just use the User field itself in the condition and apply the same ends with check.
It really depends on how your org handles incoming emails — some orgs block unverified senders at the email, so those won’t even make it to the instance. If that’s the case, then just checking the user’s email should be enough.
You can configure all of this directly in the Inbound Action condition builder. I'm adding a screenshot below to help out. Let me know if you face any issues — I’ve implemented a similar setup before, so happy to discuss further if needed!
Please Mark ✅Correct if this solves your query and also mark 👍Helpful if you find my response worthy based on the impact.
Regards,
Aniket
