- Overview
- Getting Started with UiPath Agents
- Getting Started with UiPath Agents using LangGraph
- Building a Low-Code Agent in Studio Web
- Adding Tools to Your UiPath Agent
- Introduction
- Build the API workflow
- Connect to your agent
- Test end-to-end
Run the tool-using agent end-to-end, verify autonomous API calls, and confirm the full agent pipeline.
With the tool connected and the agent contract updated, you are ready to test the full pipeline.
Step 5 - Test end-to-end
Open the Test panel using the toolbar at the top of the agent builder. Enter a quest description:
The villagers report a massive creature has been destroying farms on the edge of the forest at night.
The villagers report a massive creature has been destroying farms on the edge of the forest at night.
Run the agent and watch the Execution Trail at the bottom of the agent builder.
The Execution Trail shows the agent's full decision process. For a tool-using agent, expect at least three events: the agent's initial analysis of the quest, the tool call with the search term it chose, and the tool response with the candidate list. The agent then reasons over those candidates before producing its final output.
You should see:
- The agent calls Monster Query with a search term it chose based on the quest.
- The tool returns a list of candidates.
- The agent selects the best match and returns the five output fields.
Verify the output contains all five fields: monsterIndex, monsterName, monsterType, monsterCr, and monsterReasoning. The monsterReasoning field should explain why the agent chose this monster for the quest.
What you built
You have built the first component of UiPathfinder:
- Built a live API connector that searches the D&D 5e SRD: one input, one HTTP request, one output.
- Connected it to your agent as a tool with a single selection in the agent builder.
- The agent now decides autonomously when to call the tool, what to search for, and which candidate best fits the quest.
The two-step reasoning chain (search term selection and candidate evaluation) is exactly the kind of trajectory that produces meaningful evaluation signal; this is what the next lab is about.
What's next
- Open5e API docs - explore the full monster search API to understand what fields are available.
- UiPath Integration Service - build tools that connect to SaaS APIs without writing a custom workflow.
- UiPath Community - forums, how-tos, and developer discussion.