I am planning to create my automations with “Break large workflows into smaller components” philosophy. Because of few reasons:
- I dont know how to create my own nodes yet.
- Some “small components” will be just a bypass to get some data from http request, and due to the api request limits I want few other scenarios to “bottleneck” on small workflow so I dont break limits of the api.
- My experience in make.com suggest that creating big workflows, creates also big “technological debt” where it’s very hard to make future changes because there are too many dependencies.
Right now I am trying to plan everything ahead and also understand n8n. And the question is:
Is there any way I could create predefined data structure for those small workflows, and maybe some data structure validation to make sure these workflows will run correctly?
Thank you , best regards