I’m working with UiPath Agents in UiPath Cloud for the first time. I’ve already configured my Agent to read files using Analyze Files, and now I’m trying to invoke the Agent from a Studio workflow.
The main issue I’m facing is that I’m not sure how to pass the document to the Agent.
My Studio version is currently 2022.4, so it’s outdated and I don’t have access to the specific Agent activities. I’ve therefore been trying to use the Orchestrator HTTP Request activity instead, but I haven’t been able to figure out how to attach or pass the file in the request.
In my Studio workflow, I have the local path of the downloaded document, as well as access to the location where the document is initially downloaded. What I need is to pass this document to the Agent so that it can process it using Analyze Files.
What would be the correct way to call the Agent from UiPath Studio and pass a document/file to it?
Is there a specific API endpoint, request body, or format I should use with the Orchestrator HTTP Request activity?
Any guidance or example would be greatly appreciated!
if you’re using Studio 2022.4, that’s the main limitation. UiPath Agents and the Invoke Agent activity are only supported in newer Studio versions (24.10+), so 2022.4 doesn’t have native Agent activities.
Option 1 - Upgrade Studio
If possible, upgrade to Studio 24.10 or later. Then you can use Invoke Agent and pass the file directly to an Analyze Files input without dealing with HTTP APIs.
Option 2: Call the Agent via HTTP (works from Studio 2022.4)
You can invoke the Agent through the Agent Runtime API using the Orchestrator HTTP Request activity.
The important part is that Analyze Files does not accept a local Windows file path like C:\Temp\invoice.pdf. The file must first be uploaded to UiPath Cloud Storage (or another supported storage location), and then you pass the uploaded file reference to the Agent.
Typical flow:
Read/download the document in Studio.
Upload it to a UiPath Storage Bucket (or another supported storage service).
Call the Agent Runtime endpoint.
Pass the uploaded file reference in the request body
@AR_66 I think the main problem is the Studio version. Studio 2022.4 is quite old and doesn’t have the newer Agent activities/file input support.
Also, passing the local file path through Orchestrator HTTP Request won’t work because the Agent running in the cloud cannot access a path like C:\Downloads\file.pdf from your robot machine.
The easier approach would be to upgrade Studio and use the supported Agent invocation with a File input. Then you can pass the actual document to the Agent and use it with Analyze Files.
If upgrading is not possible, you may need to first upload the file to a location the Agent can access, instead of sending the local path directly.
Actually, you can’t do this from Studio 2022.4, since there’s no supported way to pass a file to an Agent via raw HTTP Request. Passing files from an RPA workflow requires the Run Job activity referencing the agent’s file input, and Studio Desktop 2025.10.0 or later is required for file support.
You can go through any one of these options:
Upgrade Studio to 2025.10.0 or later (or use Studio Web), then use the Run Job activity, reference the agent, and map your local file variable to the agent’s File input directly.
Route through Maestro instead of Studio, if you have Maestro access, have your process (BPMN/Flow) download the file and pass it to the agent node directly
If you cannot upgrade your studio, you’d need to fall back to a non-Agent approach for this file.
Since Studio 2022.4 is quite old and doesn’t have the Agent activities, I would recommend upgrading Studio to a supported version first.
The Agent input/file handling depends on the Agent API/version, so using a generic HTTP Request and trying to attach the local file may not work directly.
After upgrading, you can use the available Agent activities to pass the document as an input and let the Agent process it with Analyze Files.
@AR_66 take the upgrade route if possible, because you don’t have the native Agent activities available there.
If upgrading is not possible, I wouldn’t try to send the local C:\ path directly to the cloud Agent. Upload the document first to a location the Agent can access, such as a Storage Bucket, then invoke the Agent through the API and pass the uploaded file reference.
That separates the problem nicely: first confirm the upload works, then test the Agent call with that file reference.
@AR_66 You need to upgrade your Studio version; Agent activities will not work on older versions. You can try it with an RPA workflow in Studio Web if it’s a small flow or a POC and Studio isn’t mandatory.