Agent routing pattern for chatbot automation in Neuron AI (PHP)

[ololoDevs]

Hi everyone! 👋
I’m building a chatbot using Neuron AI (PHP framework) and I’d like to implement a multi-agent orchestration setup.

📌 Here’s the idea:
• The user sends a message (for example: “I want to book a meeting room for tomorrow”).
• A RouterAgent analyzes the request and determines the intent (booking, open support ticket, get some information, etc.).
• Depending on the intent, it delegates the task to the corresponding sub-agent (BookingAgent, SupportAgent, InformationAgent, etc.), each of which handles its own APIs and logic.

❓Question:
What’s the best way to structure such an agent architecture in Neuron AI — so that the Router can switch context and hand over control to the appropriate agent?
Is there a built-in routing mechanism for this, or should I manually orchestrate it using something like Router::call() or Agent::run()?

💡 Additional details:
• Each agent will have its own prompt and tools (for example, RoomService, TicketSystem, etc.).
• I also plan to maintain short-term memory across agents.

Any code examples or best practices would be highly appreciated! 🙏

[ilvalerione]

The component to create this kind of orchestrations is the Workflow: https://docs.neuron-ai.dev/workflow/getting-started

It's like n8n at code level.

The workflow make it easy to go to specific braches based on the output of an hypothetical RoutingNode.

To give you some inspirations I created a couple of example projects that implement this pattern in different ways, so you can be inspired to create your own workflow:

• Laravel Travel Agent: https://github.com/neuron-core/laravel-travel-agent
• Deep Research Agent: https://github.com/neuron-core/deep-research-agent

These are workflows with routing nodes, and multiple AI Agents. Clearly you will have your own challenges, but you have a lot of tools in your hands, like the workflow state, carry data inside custom event class, and more.

Feel free to post your feedback or questions, we are here to help.

[ololoDevs]

The component to create this kind of orchestrations is the Workflow: https://docs.neuron-ai.dev/workflow/getting-started

It's like n8n at code level.

The workflow make it easy to go to specific braches based on the output of an hypothetical RoutingNode.

To give you some inspirations I created a couple of example projects that implement this pattern in different ways, so you can be inspired to create your own workflow:

* Laravel Travel Agent: https://github.com/neuron-core/laravel-travel-agent

* Deep Research Agent: https://github.com/neuron-core/deep-research-agent

These are workflows with routing nodes, and multiple AI Agents. Clearly you will have your own challenges, but you have a lot of tools in your hands, like the workflow state, carry data inside custom event class, and more.

Feel free to post your feedback or questions, we are here to help.

Thank you so much for this amazing framework — it’s really impressive! 🙌 I’ve already started exploring it and managed to implement a workflow with nodes and several agents. Everything is working beautifully so far.

However, I occasionally run into system errors due to rate limits on Claude. Is there a recommended way to handle this? For example, could I queue up the messages or introduce some kind of retry logic?

Also, a second question — or rather, a suggestion: do you see any value in translating the documentation into Russian? I’d be happy to help with that if it’s something the team is interested in.

Thanks again for the great work!

[ilvalerione]

It's hard to manage provider limits. In the next version of the framework should be much easier to mitigate them.