I have a suggestion: As of now all the filters stop the zap when the condition is false. By just adding a check box on the filter definition that indicates wether or not the zap should stop or skip if the condition is false, many use cases can be implemented without using paths or sub-zaps. With that one could say “if condition is true, then do this next step and then continue, otherwise skip this next step and continue or stop”. Much line true if-then statement. The conditional step could still be a simple action, or it could be a webhook into another more complex zap.
Best answer by nicksimardView original