Cutting RPA runtime 95% by moving UiPath to MuleSoft

Purchase requisition and vendor data movement depended on UiPath bots driving user interfaces rather than APIs. Each run took hours, bots broke whenever a screen or field changed, failures were silent until someone noticed missing records, and the RPA layer sat on top of an already crowded integration stack, adding licence cost and a second place to debug.

• 01Traced every procurement bot to the underlying business step and identified the API or data contract each screen interaction was really standing in for.
• 02Re-implemented the workflows as MuleSoft integrations on a 3-layer API-led architecture: System APIs against the ERP and vendor systems, Process APIs owning the procurement orchestration and business rules, Experience APIs for the requesting applications.
• 03Replaced screen-scraped, sequential bot steps with direct API calls and batch processing, which is where the bulk of the runtime reduction came from.
• 04Added structured logging, correlation IDs and error handling so failed requisitions surface as alertable exceptions instead of silently incomplete bot runs.
• 05Ran the API flows in parallel with the bots and reconciled outputs before cutover, then decommissioned the procurement RPA bots and their licences.