When you have a workflow that calls a sub workflow through a tools agent and this sub workflow returns info back to the main workflow (which works perfect), there seems to be an issue though if the sub workflow contains a whatsapp send and wait for respons node. In that case the “input data” of the whatsapp is returned when the sub workflow ends instead of the actual return node at the end of the sub workflow. This was driving me crazy but I think that this is what is happening which seems kind of a bug. Has anyone tried setting up a workflow system where a main workflow (triggered in my case by a whatsapp question) calls a sub workflow where the sub workflow would ask the what’s app user to confirm a part in the middle and then at the end of the sub workflow returns data to the main workflow that is supposed to send it back to whatsapp. This works fine as long as there is no what’s app send and wait in the sub workflow, but the moment you put that in it does not work anymore as it returns the input of the whatsapp send and wait node. I’ll do some more tests on this.
Version 1.98.1, self hosted on docker.
I’m quite experienced in N8N and I’m quite sure it’s a bug.