The Call n8n Workflow Tool sub-node has been updated to version 2.0. In the workflow example below, I am unable to achieve the functionality from version 1.2, which is: routing different flows in the main workflow using the settings of the Extra Workflow Inputs and Specify Input Schema parameters. The video demonstration below illustrates this clearly.
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Hey,
please replace the Workflow Input Trigger with a new one. We have a new version there that will allow you to define your inputs there. Then they will show up in the V2 node.
Sorry for the trouble 
1 Like
Hey @ichat006, thanks so much for reaching out. Just like @c6k3 said, you’d need to delete your workflow trigger node and replace it with the new version (by just selecting it new from the plus button). This will allow you to define input fields that you can then use in your tool. Let me know if that helps or if you have any other questions.
@c6k3 @Niklas_Hatje
Thank you for the reply. I tried the new node, but it doesn’t achieve the functionality I need. Please replicate the workflow I provided above and try again.
In previous versions, each tool had the “Specify Input Schema” option.
The workflow example in the documentation has not been updated either, as shown in the image below.
Hey @ichat006, I took your example from above and changed it accordingly. Let me know if that makes sense:
Good point regarding the docs. We will update that!
1 Like
Thank you for your help.
Now, I understand that to achieve the functionality of version 1.2 in version 2.0, it is necessary to define the variables for all tools in the “When Executed by Another Workflow” node. This implementation seems less simple and intuitive compared to version 1.2.
Additionally, I discovered an issue: in a workflow, you cannot mix nodes from these two versions. All tool nodes must be redefined entirely.
Hi @ichat006, yeah I can see how this feels unintuitive when you’re used to the old paradigm. I believe you will get into it once you’ve used it. We user tested it quite extensively and saw that new users got the hang of it much easier than before. It should also help you to have a better overview of what tool does what exactly.
Regarding the mix of nodes: That’s a real issue unfortunately. Our node versions are quite powerful to allow users to keep using their versions, but it also makes it hard to ship core changes to them. We will definitely take this as a learning and try to have a better migration next time.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.