I have a main workflow that has a Slack webhook as a trigger that then flows into a Tools Agent node. This Tools Agent has a “Call n8n Workflow Tool node” that points to a subworkflow which has a Slack “Send and Wait” node. The purpose of this Slack node is to send a question to a team member, wait for them to answer, and once they answer the “Send and Wait” node" resolves. I can even see the output data for this node. However, this response doesn’t get sent back to the AI agent. When you check the output log for the AI Agent, you can see that it was able to invoke the subworkflow properly, but the output only shows the parameters passed on from the AI agent tool and not the response from the last node (send and wait). The note from the “Call n8n Workflow Tool node” states: “This tool will call the workflow you define below, and look in the last node for the response. The workflow needs to start with an Execute Workflow trigger”. It does execute properly, the issue is that the response doesn’t get sent back to the AI Agent.
I noticed similar issues, so I implemented a route which checks that thread, I think it was by time stamp, and would monitor reply count, if it increases, I would pull reply, and then process, not straight forward, so hoping this is fixed soon.
I tested with not tool node, that works and sends message and approve works, but seem the ai agent just hangs on wait.
Hello,
I have a similar issue with a simple “Execute Sub-workflow” node. The node’s output corresponds to its input instead of the values returned by the sub-workflow.
Here is a test workflow node JSON:
Do you have a solution? I need to call this sub-workflow from multiple workflows.
Tested with version 1.99.1, and the issue still isn’t resolved.
Alternatively, I attached a Slack “Send and Wait” node directly as a subnode to an AI Agent. When the subnode is called, the message gets sent to the user, but when they click on the Respond button to fill out the form, the page says “No action required” and there are no fields to fill out.
I am experiencing the same problem with the Telegram send and wait node. There seems to be something wrong with getting the form that is filled back to the master workflow. It’s outputting all the data correctly, but not bringing this back. I’ve tried a set fields, code block, and no operation do nothing module at the end, but nothing seems to work ;-(
btw, my workaround was not connecting via a tool and just using a normal node, and also using a wait note, which created a new form for replies etc. Maybe this will work for time being.
I’m experiencing the same issue in version 1.109.0. When a subworkflow contains a ‘send and wait’ node, the ‘Execute Workflow’ node returns the input instead of the subworkflow’s result, even though the subworkflow runs successfully. This same issue occurs when a workflow tool node uses a ‘send and wait’ node; the AI Agent node also returns the input.
Issue persists in 1.112.4. SendAndWait nodes are still broken when used as a tool for an AI agent or if contained in a sub-workflow that is given as a tool to an AI agent.
Hey, I confirm this is a bug and will not be fixed until maybe the next major n8n version. Any nodes that have a wait functionality and are part of a sub-workflow will cause the sub-workflow to not return any data back to the main flow.
You will need to explore workarounds like this or others:
generating a unique ID from the main flow
passing it to the sub-flow
sub-flow persists the final data in a DB (with the unique ID)
main flow reads the data from the DB using the unique ID
Sorry it’s not the desired outcome. Would appreciate if you mark this as Solution if it helped understand the issue.
