I have a flow in N8N where a primary agent is connected to another agent whose role is to send 10 questions to the user and generate a report.
In other words, the user contacts the primary agent, and they choose option 1 to speak to the secondary agent to initiate the service.
The problem is that at a certain point, instead of directing requests to the secondary agent, the primary agent consults their own memory node and asks the user questions, instead of directing the request to the secondary agent.
I’m using this flow, but I’ve tried it with the call node n8n workflow tool, and the same behavior occurs.
Is there a way to force the primary agent to bypass their memory node and direct all requests to the secondary agent?
Information on your n8n setup
- n8n version: 1.112.4
- Database (default: SQLite): Postsgre
- n8n EXECUTIONS_PROCESS setting (default: own, main): own
- Running n8n via (Docker, npm, n8n cloud, desktop app): Docker / Portainer
- Operating system: Ubuntu