Yep, as others have said, I think the big need here is to _not_ apply the automation to every level of task. Even if you could set it so the automation only applies to a certain folder or list (or task level, I suppose), that would do the trick for our purposes. Particularly with nested subtasks I could see the "not subtask" criterion becoming a little cumbersome, as you'd always have to be aware of what level of task creation you're on. "Apply to this folder/list/task level only" might help.

Yes! This is super annoying when you have Templates applied by an Automation. I can't think of a time it is ever useful to have the same Task Template applied to all its subtasks. https://www.loom.com/share/e4b8e6118db8400c806fb785e01939aa

Hoping they are also working on "is not subtask" as a condition.

Goodness! This is SO important! I like Matt Kinsel's suggestion that the condition be: is/is not subtask. Right now if I want all new tasks in a given list to use a template, great -- I can automate that! But then, if someone creates a SUBTASK within that task on that list, it gives that subtask the same template. MADNESS..... PLEASE CONSIDER THIS! Thanks!

I would like to be able to automate based on the status or assignees of a subtask. Exactly like with a task, same conditions and actions but for a subtask.

Yes, please allow do differniate the triggers between "task created" or "subtask created" because currently this messes up my workflow because the automation that runs for "task created" actually shouldn't run for a subtask.