I think you've missed some real limitations that have prevented us using Low-code / No-code solutions in practice. In essence he solutions are based around a single identity that creates, deploys and maintains them. Fine for working on your own but when in an enterprise you need to handle:

1. Security, the solution needs to respect the identity of the logged in user not use its creators identity.

2. Security, if running unattended then it needs to use some form of Service Identity (not a 'service account') with restricted scope.

3. Deployment, if it will be used on test data, and if not the ability to affect production data with untested code should be making you very, very nervous, then it needs to be deployed at least twice (DEV and PRODUCTION), but NC/LC often lacks any form of deployment automation.

4. Deployment, if it will be used in multiple places in PRODUCTION if the deployment can't be automated then we have found that about 30% of the instances fail due to configuration issues.

5. Maintenance, frequently these are tied to the user who created them and when that user's account is disabled then they stop working.

6. Maintenance, there is no form of automation testing available so when version 2 comes around checking it hasn't broken thngs is very hard.

In short we tell our users that its like an Excel macro, you can create them but they belong to you and you are responsible for them. As a result they get used for very simple tasks, much like email rules...

Technical Director for Simple Innovations Ltd. First paid for code in 1980, but still has all his own hair.