In this article we're going to further explain the relationship between triggers and filters with a real-world scenario. We'll create an example Automation Task and point out correct and incorrect strategies for achieving a goal. If you'd like to read more about creating effective Automation Tasks than this support article has got you covered.
The Goal: In this scenario Acme Co. would like to immediately send a "Thank You" email to marketing agencies when they fill out the "Crazy-Egg-Magic-Trick" form.
Correct (One Trigger, One Filter): In this example we should set the action of filling out the form as the trigger and then filter out marketing agencies from the form-fillers. Check it out in the screenshot below.
Now, Imagine if we reversed the trigger and filter in the screenshot above or created both rules as triggers. Would we achieve the desired goal? No, the resulting automation task wouldn't work correctly. In fact, it would send emails every time the "Marketing Agency" field in Contact Manager changes from "no" to "yes". Let's take a more in depth look at the all-to-common "two triggers" approach.
Incorrect (Two Triggers): Triggers should be used sparingly in SharpSpring. If we were to add both of these rules as a triggers we would likely have unexpected results. Consider the scenario where Bif the sales guy fills out the "Crazy-Egg-Magic-Trick" form. A few months later Bif decides to career pivot and apply for a job at a digital marketing agency. Acme Co. recognizes this and changes the "Marketing Agency" field in Contact Manager from "no" to "yes". Bif is now a marketer that has filled out the "Crazy-Egg-Magic-Trick" form. The workflow that sends an email to thank Bif for filling out the form is finally set off (a few months too late). Bif is gets a random email and is confused.