We were founded in 2005 in a tiny apartment in Bucharest, Romania as DeskOver.

Fittingly, it was a customer who, in 2012, first saw the immense possibilities for us in the fledgling RPA market. Our desktop automation product launched in 2013. In 2015, we introduced our enterprise platform along with our new name.

Today, UiPath is the fastest-growing enterprise software company in history with scores of offices, thousands of employees, partnerships with the world’s best consulting and BPO firms, a 500,000-strong developer community, and 5MM+ robots at work in over 5,000 global enterprises.

Our mission is to deliver the leading Robotic Process Automation platform to our clients for an automation first mindset.

We build software robots that automate repetitive processes. Our software robots take on the tedious, mind-numbing work and free people to do the more stimulating, creative work worth doing.

But no matter how much we’ve grown, one thing hasn’t changed. We’re still building a company we love to work for

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.)

O-trigger

O-trigger

Help

How To