RPA vs API - How RPA is Technical Debt

RPA is automating the user interface of e.g. Windows (/web page) and an API is a direct connection between two computers/systems. If you use RPA, your robot will break, if the Windows application or webpage is still being developed on.

Knowing something will break in the future is called technical debt. That's why using APIs I always better because most developers agree, you don't make fundamental changes to an API. But using an API is not always an option, and that's why we have RPA - and that's awesome.

- Join my network with +2500 RPA Developers, where we solve RPA problems, network, and help each other upgrade our careers. It's free!

FOLLOW ME:

MY GEAR (Amazon affiliate):
🖥️ My monitor

💡 Lights

⌨️ Keyboard

📹 Camera

🎤 Microphone

#rpa #shorts #automation

[gahshunker]

API first - that's definitely the rule. But still, I'm amazed at UiPath's 'Anchor-base' capability to allow for plenty of wiggle room in UI changes. Coupled with dynamic selectors, and several fallback methods, you really have to mess a website UI to break a proper bot

[Yo-yxwo]

You can use APIs in rpa, there are rpa background processes.

[SanderBK]

Always API first, but I can think of many cases where data is extracted from multiple sources and combined by rpa and then send to the target application via an API.

[kavyas]

Hi Anderson,
Sir could you please make a video on how to cut a row in one sheet of the Excel and paste in another sheet based on some if conditions eg: cut data i.e., a row from main sheet and move to ended-sheet name