the new ‘execute a Sub workflow’ has a great selector so you don’t have to copy routine IDS anymore
in Exchange it seems that you have to manually link every single field that you are passing in?
is this seriously the plan because I am not linking up 20 plus items manually
Hi @bally If you do not want to manually select all those fields , in your sub workflow trigger you can set it as:
And so whatever your main flow sends as data you do not have to map those into your sub flow.
Although in your main flow you have to map those as it requires you to map each field explicitly.
I was going to add on, I added the split out node just so you can see that you can seperate them after if you want to manually map anything.
Hope this helps!
Check it out here: How to Use Sub-Workflows in n8n
OK this seems really confusing. The subflow trigger did not change, or at least I didn’t have to delete it and create a new one.
it’s currently got pinned data so I have
it’s the caller that wants me to link up all of the fields manually, if I don’t map them or remove them
so this node is strangely controlled by the Sub Workflow node which seems completely crazy…
what happens if I have set this up correctly for now but later I the sub node?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
