Unable to Find Published Workflow in Agent Tools (UiPath Web Studio)

Help Studio Web
1

Hi Community,

I need help regarding an issue with UiPath Web Studio and Agent Workflows.

I have published a process from UiPath Studio to my Orchestrator Tenant successfully. The package is visible in Orchestrator under Processes/Packages.

However, when I create an Agent Workflow in UiPath Web Studio (Agentic AI → Agent → Tools section), I am not able to see my published workflow listed under the “RPA Workflow” tools. It shows “No tools found”.

I am trying to understand:

  1. Why is my published workflow not appearing as a tool for my Agent?
  2. Is there any specific configuration required so that workflows published from Studio can be accessed as tools inside Agent Workflows?
  3. Do I need to create the process under a specific folder or enable any API connections/permissions?
  4. Are there limitations on which workflows can be exposed as tools to the Agent?

Any insights, required configuration steps, or troubleshooting tips would be greatly appreciated.

Thanks in advance for your support.

image
image1901×948 139 KB

2

Hi @Shivubhaskar79

Welcome to the community

Your published workflow will not appear in Web Studio Agent until you explicitly expose it as RPA Tool in Orchestrator.

You can see here

Cheers

3

hii @Shivubhaskar79

Your workflow isnt showing up because it usually published in the wrong folder missing permissions or has unsupported argument types.

Make sure you publish it to a shared orchestrator folder the agent can access give your userobot the right permissions and use simple input output arguments.

After that the workflow should appear as a tool in the agent.

4

@Shivubhaskar79

welcome to the community

you need to create a process using that package then it would be visible as tool

publishing of package will not create the process

cheers

5

Create a process as publishing to Orchestrator only won’t work.

Nothing except publishing and create a process.

Yes create a process in any folder accessible to agent resources.

No such limitations. Any process created on the Orchestrator can be used as a tool.