External application is a ticketing application, whenever a specific ticket is approved, it sends a post Api call with the body needed. UiPath bot needs to be triggered when that call is received and pick the body and process.
Let me know how we achieve this using UiPath orchestrator Webhook.
Hi @Sasikanth,
You cannot make Orchestrator itself receive arbitrary POSTs, so the usual pattern is: expose a small HTTP endpoint that receives the ticketing app POST, then have that endpoint call Orchestrator’s Jobs API to start the robot and pass the POST body as input arguments.
In short: host a webhook receiver (Azure Function / AWS Lambda / lightweight web service) that accepts the ticketing app POST and validates it, obtain an Orchestrator access token (OAuth2 client id/secret), and call the Start Jobs API (POST /odata/Jobs) with the ReleaseKey, an appropriate Strategy (e.g. Specific), the target Robot/Environment, and pass the ticket body as JSON in InputArguments. The robot receives the InputArguments in the process and processes the ticket. Also secure the endpoint (TLS, IP/secret validation) and use the ReleaseKey and Environment from Orchestrator; test with Postman first to confirm the Start Jobs payload and token flow.
But in order to create a webhook receiver either in Azure/AWS, we need that account and details so and so. This seems quite a lengthy process as this involves multiple teams from cloud. So, before I go to client and ask this…is there any simple approach that we can try?
If you want to avoid Azure/AWS and avoid involving cloud teams, you still need some endpoint to receive the POST. Orchestrator itself cannot act as a public webhook receiver. The simplest alternatives are:
1. Host a small local listener on a server or VM that you already control. A lightweight Python/Node.js/PowerShell HTTP listener can receive the POST and immediately call Orchestrator’s Start Job API. This avoids cloud teams; you only need a machine that is always on and reachable.
2. If the ticketing tool supports sending email on approval, you can trigger the bot through the Email Trigger in Orchestrator or a mailbox monitoring workflow. The bot reads the mail, extracts the payload, and starts processing. No web endpoint needed.
3. If the ticketing app can write to a shared folder or database, monitor that with a file trigger or queue trigger instead of receiving a POST.
If none of these are available, then creating a proper webhook receiver in cloud is the only option.
as its on prem then only way you have is use a middleware which can receive the webhook event and then call UiPath start job api to start job on UiPath..