After nearly 100 hours with hundreds of research tabs and dozens of attempts, I’m still not 100% clear on the mechanics of n8n workflows (which could also be hindered by other similar tools I’ve used that require the user to build their own iteration logic themselves.)
Whichever it may be, it’s likely my use case could do with NOT utilizing n8n’s built-in automatic item iteration (as that seems to cause the issues) so as a side question, I’d love it if anyone had any ideas as to how to disable it throughout the workflow?
There is only a couple of nodes that I need to iterate through but I have yet to find out a way to force the index being used (which the flow determines based on other factors) so if anyone knows, that’d be great too.
So to the main question… I’m not sure how helpful it would be to post a full sample as what I currently have is such a mess with dozens of nodes - really just the theory/method would probably help set me off down the correct path.
Below is a very basic representation of the part of the workflow which I can’t get to work. Perhaps one of you lovely people may have some ideas about how to structure it?
Any help whatsoever is deeply appreciated so cheers in advance!
- n8n version: - can probably find out
- Database you’re using (default: SQLite): - can probably find out
- Running n8n with the execution process [own(default), main]: - can probably find out
- Running n8n via [Docker, npm, n8n.cloud, desktop app]: - heroku