This is what I see when I try to trigger the sub-workflow - the inputs do not appear. I’ve tried switching to JSON format to see if that would change anything, but still nothing shows.
The weird part is sometimes I can see the node “Fetching Inputs” very quickly before it dissapears and shows nothing.
I’ve tried deleting the nodes and placing again, restarting my instance, nothing seems to help.
Not sure what other troubleshooting steps I can try so I figured I’d post here and see if anyone has any ideas.
I have tried it and ran in the same issue on how to actually pass down the data, so now i use a workaround which is using an AI Agent and give it a tool which is Call n8n Workflow, so with that the AI can call the workflow and can pass that data down, and what i do is that in the workflow which is to be executed i add some mock data to test it with and then let AI Agent node handle it, and it works for me something like
I still cant seem to find any direct workaround that i can just pass data with the Execute Sub-Workflow, you should give this approach a try, let me know if this helps
Thanks for the tip @Anshul_Namdev I’ll give that a go and see if I can get it working. It’s unfortunate that this workaround is required in the first place, seems like this should be a fairly simple function to get working. I’m also surprised I haven’t seen more people run into this exact issue.
Once I’ve tried out your method I’ll let you know how it goes.
@Anshul_Namdev I believe I’ve just found a solution! I just went to give your method a try and saw a new warning in the GUI I hadn’t seen before, it said that the sub-workflow wasn’t published so could be used for testing but must be published before use in production. Out of interested I published the subworkflow, and I can now see the input fields!
Oh that’s nice! Publishing the sub-workflow and then using that, i haven’t tried that but that is really cool to know! As of my project i just give bunch of other workflows which have different roles, so it just works for me! Indeed this is nice when passing down some important data! Let me know if you need any help with that!
Yeah most of the time people do not need to transfer data between workflows, they use the sub workflow functionality as a tool call, so this makes a big workflow pretty easy to handle, and yeah this is nice approach but it still can cause a lot of troubles between multiple flows if we transfer data like that, just keep the data around in the same workflow or just use a data base.
