There is no direct trigger in UiPath to monitor a database for record changes.
You can create an RPA workflow that periodically checks the row count or looks for newly added/updated records in the database. Once new records are found, the workflow can add them to a Queue, and the bot can process the Queue Items.
Hi @Deeksha ,
Try this approach once if it helps:
Database INSERT/UPDATE → call an Orchestrator API Trigger → start the UiPath process → bot reads and processes the changed record. API Triggers are specifically designed to start an automation through an HTTP request.
Alternatively, push the changed record into an Orchestrator Queue and use a Queue Trigger to start the bot when a new item arrives.
For reliability and scalability, I would prefer the Queue Trigger approach, especially when multiple records may be updated.
Another approach is to use a database polling + Queue Trigger design.
Database INSERT/UPDATE → UiPath checks for changed records → Add record to Orchestrator Queue → Queue Trigger starts the bot → Process the Queue Item
You can use a CreatedDate / ModifiedDate column or another unique identifier to identify only the new or updated records, instead of checking the entire table every time.
This approach also helps with retry, transaction tracking, and handling multiple records reliably.
If your database supports it, you can also use a database-side trigger/event mechanism to call an API or middleware, which can then trigger UiPath.