UiPath
UiPath agents ask the right person, or your policy, before they act. Robots wait for a decision made in Deliverd and carry on when it is made.
There are two ways in, and you can use both. A UiPath agent reaches Deliverd as an MCP server, with nothing to install. A robot (an RPA workflow) hands Deliverd an Action Center external task and suspends; Deliverd completes that task when a person decides, and the robot resumes.
UiPath agents, over MCP
Orchestrator can register a remote MCP server so agents built in Agent Builder, Maestro and Studio Web can call its tools. Deliverd signs the agent in with an agent key sent in a header, so the requests show the agent as the requester and your agent permissions and standing rules apply.
- 1
Issue an agent key
In Deliverd, open Agents → Agents, add an agent for UiPath (or pick the one that will ask), and issue a key on its page. Use an agent key, not a personal one: a request made with your own key cannot be approved by you.
- 2
Keep the key in Orchestrator
In Orchestrator, add a Credential or Text asset named
DeliverdAgentKeyin the folder your agents run in, holding the key. - 3
Add the MCP server
In Orchestrator, open the folder, go to MCP Servers → Add MCP Server, choose Remote, and fill in the form with the settings below. Orchestrator masks the header value once saved.
- 4
Give the agent the tools
In the agent, add the Deliverd MCP server as a tool source and turn on
request_approval,get_approval,check_gateandget_gate. Tell it, in its instructions, what to ask before which action, and to carry on only once the answer is approved.
Type: Remote Name: Deliverd URL: https://deliverd.dev/api/mcp/v2 Header: Authorization = Bearer %ASSETS/DeliverdAgentKey%
UiPath robots: pause until a person decides
A robot creates an external task in Action Center, tells Deliverd about it with the request, and suspends. While it waits it holds no robot. When the approval is decided, Deliverd completes the external task in your Orchestrator, and the robot resumes with the decision as the task's action.
Connect UiPath (once, as an administrator)
- 1
Create an external application
In UiPath's Admin portal, open External Applications and add an application. Make it a confidential application, add the Orchestrator API application scope
OR.Tasks, and save. Copy the App ID and App Secret. - 2
Let it reach your robots' folders
In Orchestrator, give the application a role in each folder your robots run in that can view and edit tasks.
- 3
Connect it in Deliverd
Open Connect → UiPath, paste your Orchestrator's address (the one in your browser, ending
orchestrator_), the App ID and the App Secret. Deliverd signs in with them before it keeps anything, and keeps the secret sealed.
In the workflow
- 1
Create External Task
Add Create External Task with the External Tag
Deliverdand a title. Deliverd only completes external tasks with that tag. - 2
Ask Deliverd
Add an HTTP Request to
POST /api/v1/uipath/taskswith an agent key, the request (the same fields asPOST /api/v1/approvals) anduipath.taskId, the task's id. Adduipath.folderPathoruipath.folderIdfor the folder the robot runs in. A 201 means people are being asked; posting the same task again returns the same approval. - 3
Wait For External Task And Resume
Pass it the task from step 1. The robot suspends here until the decision is in.
- 4
Branch on the action
When it resumes,
TaskActionisapprove,reject,changes_requestedorexpired. Carry on only onapprove, and run withinputfrom the task's data: it holds anything the approver corrected.
POST https://deliverd.dev/api/v1/uipath/tasks
Authorization: Bearer <agent key>
Content-Type: application/json
{
"title": "Pay invoice INV-2291 to Northwind Ltd",
"description": "Northwind's bank details changed last week. Amount €18,400, due Friday.",
"risk": "high",
"approvers": [
"Finance"
],
"input": {
"invoice": "INV-2291",
"amount": 18400,
"currency": "EUR"
},
"uipath": {
"taskId": 1378,
"folderPath": "Shared/Finance"
}
}The task's data when the robot resumes:
{
"decision": "approved",
"approved": true,
"decidedBy": "Ann Byrne",
"decidedAt": "2026-11-18T14:02:11Z",
"note": "Called Northwind to confirm the new account.",
"approvalId": "8a1c…",
"approvalUrl": "https://<your Deliverd address>/approvals/8a1c…",
"input": {
"invoice": "INV-2291",
"amount": 18400,
"currency": "EUR"
}
}| Action | When |
|---|---|
approve | The approval was approved. Run with input. |
reject | Someone said no. note says why. |
changes_requested | Someone asked for changes. Make them and ask again with a new task. |
expired | Nobody decided in time. |
For the security review
- Agents and robots sign in with an agent key, kept as an Orchestrator asset. Nothing a robot sends can approve anything: every decision is a person's.
- The external application's secret is entered once by an administrator, sealed at rest, and used only to sign in, read the task a robot names and complete it. It is never shown again or sent to the browser.
- Before asking anyone, Deliverd checks the task is an open external task tagged
Deliverd, so a robot cannot point it at somebody else's task. - Calls to Orchestrator go over https to a public address only, with no redirects. A decision that cannot be delivered is retried; the task can always be completed by hand in Action Center.
- Disconnecting removes the secret. Robots still waiting stay suspended until someone completes their task in Action Center.
Try it on your own agent.
Free to start, no card. Sign up with Google, Microsoft or GitHub, and the first page after hands you an API key.