**YouTube** is an American [online video-sharing](https://en.wikipedia.org/wiki/Video_hosting_service "Video hosting service") [platform](https://en.wikipedia.org/wiki/Web_platform "Web platform") headquartered in [San Bruno, California](https://en.wikipedia.org/wiki/San_Bruno,_California "San Bruno, California")

cf3f59da-c081-4fab-99d2-f02e60e183b0.PNG

d0b8d8ab-4597-45c0-b4fb-66ab888e04c1.zip

UiPath Orchestrator provides an out of the box trigger mechanism that allows to start processes at a specific time or when a queue item is added to a queue. This can be limiting in scenarios where you want to chain processes (when process A is done, start process B), or react to unexpected events (process failed, schedule did not start). 

O-trigger aims at solving these scenarios by allowing you to create triggers based on Orchestrator events.

O-trigger is designed around the Webhook feature of Orchestrator. Webhooks allow you to configure endpoints where Orchestrator will post data when an event occurs. For example, when a job fails, Orchestrator will push some data regarding the failure (name of the Robot that failed, name of the process that failed, etc.) to all the configured Webhooks.

O-trigger is a web server that can listen for Webhook events and respond with actions. Namely it can send emails and start jobs on Orchestrator when it receives specific events.

Extends the triggers possibilities of Orchestrator, allowing users to trigger jobs based on various Orchestrator events (job failed, new queue created, new robot created, etc.)