Hey all,
let me try to help with some of the confusion: We changed how the sub-workflow tool works in n8n a bit: Instead of defining a schema in the tool call, you can now define the data you expect directly in the sub-workflow: Think of it like a function in code where you define arguments.
This allows you to have a tighter fit between agent and the workflow tool and a better overview over what you need to input here.
Generally, you want to define the expected inputs in the sub-workflow trigger, like below, with whatever data the Agent (or you) should provide
When calling the tool, you can then decide if the values should be provided by the Agent or if you want to pass “hard-data” into the tool
Please let me know if think that does not make sense for any of your use cases.