Route to agent ends the flow and routes the conversation to another agent, which continues from there. Use it when the flow's logic decides who takes over: the step always routes to the agent you configured, so the choice is made by the tool, not by the model. For transfers to a human agent or another system, use the Handover step instead.
Route to agent ends the flow, so it takes the place of a Return result step.
Target agent
The agent that continues the conversation after this tool finishes.
Output type
Choose whether the target agent gets a result from this tool.
-
No output: route without passing a tool result to the target agent.
-
Text, JSON, and JMESPath expression: build a result the target agent uses as input, exactly as in Return result.
Contexts and Media
Also as in Return result: store variable values in contexts so agents and other tools can use them for the rest of the conversation, and attach media as extra knowledge for the target agent.
In the conversation log
The switch shows as an agent handover, marked as routed by the tool. This makes it easy to see in the log which agent changes came from deterministic routing and which came from the agents' own decisions.