Thanks for the mention, @IvanStaykov!
As you say, the main problem with setting up rules based on form submissions is
Of course if every new task in a project will be coming from a form submission, it’s not a problem, but if, as it sounds like is your scenario, a project will have a mix of form-created and non-form-created tasks, it’s an issue to distinguish for rule use.
One alternative is what @IvanStaykov mentions of a special “buffer” project; i.e. a special project only for form submission purposes. (IMO this is a good potential solution when form entry is being done by supplying a direct link to the form; not so much when you want users to be able to create forms when they’re sitting in the actual target project.)
Another option which uses my Flowsana integration: if you can set up the title of your form submissions such that they contain a unique string of text that users won’t ever type when they create non-form-related tasks in the project, then you can use Flowsana’s “task contains a matching word or phrase” rule condition to trigger a Flowsana rule based on it seeing that particular string of text and thus knowing that it must be coming from a form submission.