r/rpa • • Jul 09 '20

News The perfection

Post image
86 Upvotes

r/rpa • • Nov 17 '24 Heart of Silver

🚀 The Evolution of Automation Buzzwords

Post image
56 Upvotes

"Quantum Agents Revolutionize Automation" or "Sentient Automation: The Future is Self-Aware Workflows." Can't wait to see these trends take over next!


r/rpa • • Jan 03 '25

RPA user since 2008, my two cents on the past and future of RPA -

55 Upvotes

I’ve been using RPA since 2008, even before the word RPA was coined so I’ve seen my share of changes.

I keep seeing posts about the future of RPA and here are my 2 cents about it.

Tech is a tool to get things done, cut costs or improve productivity. Keep your focus here not on the tech that you know.

Will RPA have a future? Yes where you need 100 percent accuracy or have a well defined procedure. AI currently doesn’t show it’s work, like RPA where you have traceability. But that could change in the future.

I also suspect AI will get expensive in the future. Right now it’s being subsidised by investor money.

So, keep your focus on the right things, keep looking out for new things that help you get there and you should be fine. All the best!


r/rpa • • Mar 06 '26

I got hired to automate an entire company and I have no idea where to start.

44 Upvotes

Honestly, I could really use some guidance on this, so I'm not sure how often I'll be posting here. Less than a week ago I was hired as an intern at a mining company. Right now I'm working across the administrative, finance, and legal departments. The first few days were pretty straightforward — just some Excel file improvements that I managed to handle and am almost done with. But a few minutes ago I had a meeting with my boss, and everything changes.

Turns out they want to go about thirty steps further: they want me to automate the entire company. We're talking Excel, reporting, payroll, accounting, and a whole range of other processes. They seem to think I'm an expert at this and that I have the skills to pull it off. Spoiler: I don't. I have a basic programming background and I'm comfortable with tools like Microsoft Office and the main AI platforms out there right now. But beyond tweaking formulas and setting up patterns, I genuinely have no clue about automation. And don't even get me started on databases for historical record-keeping — that's completely foreign to me.

The truth is, I'm pretty stressed out. This is a task I'm not prepared for, and I don't even know where to begin — what to learn, how to approach it, or how to execute it. I seriously need some advice, because right now the entire company runs on manual processes (and I mean everything), so I just want to get a foothold somewhere. I want to start picking up the right vocabulary and understanding the right concepts so that somehow, six months from now, I'll still have a job.

Can anyone help me out?


r/rpa • • Nov 26 '22

Software Dev vs RPA Differences in Approach

39 Upvotes

A few things I have noticed when bumping in to SW dev people and how they think RPA is to be developed:

  • SW Agile Dev: I find the Agile approach in RPA is the wrong approach. My experience is RPA dev is better in line with Waterfall approach. It may be the way I guide my team to build as I look at it as a mechanical/production line system. We may only take a few days to a few weeks to build the process, but can spend months on qualification to tune and understand what exceptions are, volume, etc.

  • Robots should be processing with 100% success: This thought is absolutely false. Exceptions are part of the game. The questions is what does an exception look like and at what volume. People that sell robots do 100% of the work put themselves in a bad position. The robots will be interacting with systems that they have no control over.

  • Automated RPA Testing: SW can dev automated tools to test their SW. Can's RPA do that? No. We have to physically watch it run through things from beginning to end. There are no short cuts. Would be nice.

  • Deploy and Forget: Robots at best are 2 or 3 y/o kids. Like any production line, they must be constantly monitored. Not necessarily meaning watching the process, but watchin the logs and more importantly the queues. During Qual we get a profile of what the exception volume is suppose to look like. If its <= to that profile, it is a good run. When we see it go above the profile, that triggers checks to work out what happened

  • For the Robots it is French Law standard: Meaning, the robots are guilty until we prove they are innocent. This is a big problem as we can burn days having to go through logs, data, testing etc to show that robot did nothing "wrong" (For some reason people think the robots become self aware). Find out it is due to other system or bad data was provided etc. I find this to be the #1 drain on my team now.

  • Quick Fixes: You just add a line of code and it's ok.....Some cases yes, many cases NO. We have to separate is this a logic issue (that we write mainly in python) that we can make some changes to and update. Where it gets complicated is when there is a mechanical change (UI change/process change etc), that impacts how the work gets done and requires a complete requalification.

Anyone seeing other differences?


r/rpa • • Nov 04 '19

Microsoft Announces It's Own RPA Platform

37 Upvotes

r/rpa • • 12d ago

Did I just waste 4 years of my life building shitty automation for clients?

35 Upvotes

Which all of them are obsolete now.

This was me reflecting on my 4 years of working on a technology called RPA.

It's kinda like AI now. It generates docs and sends emails, but it took 10x longer to build and broke half the time.

In 2026, what took a team of 20 people to build can be done in a month with AI.

It's a reflection of how far things have progressed.

But at the same time, I'd never trade my time building caveman AI automation.

I'm grateful for that experience. It led me to the career I have today.

Anyone else been through something similar?


r/rpa • • Jun 19 '26

28F, 4 years in RPA, feeling stuck and questioning my future in tech

32 Upvotes

Hi everyone. I’m a 28-year-old woman working in IT in France, and I’m feeling completely lost about my career. I studied computer engineering and started working in RPA right after graduation.
I’ve been doing it for about 4 years now, mainly with Automation Anywhere and Blue Prism. The problem is that I don’t really enjoy what I do anymore, and the more I think about changing careers, the more I realize I don’t know what I actually bring to the table. RPA is such a niche field that even many people in IT don’t really understand what we do on a daily basis, which makes it difficult to explain my experience or see how it translates to other roles.
After 4 years, I expected to feel confident and technically strong, but instead I often feel the opposite. Sometimes I genuinely feel like a fresh graduate could have stronger technical foundations than me. I know I’ve gained professional experience, but when I look at other areas of tech, I don’t feel like I have the skills needed to make a move. Technology is evolving so fast, and I constantly feel behind. Lately I’ve been considering switching to QA, but I’m not even sure if that’s the right direction or if I’m just trying to escape a job that doesn’t suit me. Has anyone else been in a similar situation, especially after spending several years in a niche field? How did you figure out what skills were transferable and what career path made sense next?


r/rpa • • Aug 26 '26

RPA is boring (unpopular opinion?)

30 Upvotes

I started RPA dev in 2016. Back then it was exciting, learning new tools (Blue Prism, UiPath, etc). The builds were fulfilling and client reactions were rewarding.

After 10 years of building bots, the irony hits hard. This shit is mundane - one of the core traits of why we automate process.

I remove repetitive, mundane tasks from clients, by doing repetitive mundane tasks myself.

Are any of you seasoned RPA devs still enjoying what you do?


r/rpa • • Nov 30 '23

RPA with python

30 Upvotes

Am I the only one out here who thinks custom automations created with python are much more powerful, more capable, and easier to maintain then no-code services like uipath, Microsoft PA, etc?

As a developer, it seems like things are so much more complicated in those softwares compared to just writing code with selenium or playwright, and external APIs, and hosting these scripts on AWS for clients.

Does anyone agree?


r/rpa • • May 27 '22

Is it too late to get into the field of RPA in your 30's without any IT background?

29 Upvotes

Hi guys,

Good day!

Ever since 2 years ago, I am so fascinated with RPA because my friend always talks about it. Been watching youtube about it as well. I want to get into the RPA field, but I asked my friend about it, he said it's already too late for me, I'm 32 years old without any IT background. So, I just want to get your 2nd opinion about it. What do you guys think?

With the fast changing world we live in right now, I want to get into the field where the future is going as well. and for me, that is RPA. I work in Social Services right now, but I really want to get into the RPA field.

If possible, do you think taking UIPATH course is enough? What else do you guys suggest? And what is your opinion in the RPA job market for the next 5-10 years?

Thank you so much, I really appreciate this. Bless you all.


r/rpa • • Oct 23 '19

UIPath Fires 500..

Thumbnail google.com
29 Upvotes

r/rpa • • Sep 09 '26

LiberRPA 0.3.0: visual process design with Python in VS Code

27 Upvotes

You've inherited a working automation. Now a business rule changes. Where should you make the change, what else could it affect, and how will you check the result?

I'm the developer behind LiberRPA, an open-source RPA toolchain for Windows. My goal is to give the next developer a visible process to follow and ordinary Python code to work with.

0.3.0 is available. Its flowchart controls execution, with Blocks linked to Python files in normal VS Code editor tabs. You can edit and debug the implementation, run one Block or the whole flow, and package it for local execution.

Visualize the process. Code the logic.

Put each change where it belongs

Changes to the logic within a step can stay in Python. Changes to the overall sequence or branching can be made in the flowchart. You can review changes to the Python implementation through ordinary Git diffs.

You choose how much each Block does, and compatible Python libraries remain available when you need them.

Investigate with the project in view

When a run behaves unexpectedly, understanding a step's code may not be enough. You also need to know how that step fits into the flow and what happened during execution.

LiberRPA's JSON flow definition is the model it actually executes. You can examine it alongside the Python files, documented execution rules, selectors and run logs.

That also gives a general-purpose AI coding assistant of your choice useful context for investigating a problem and suggesting changes. LiberRPA's own source is available if the investigation leads into the framework.

For production work, I believe an experienced developer still needs to own the architecture, review changes and verify the business result.

Keep the surrounding tools together

LiberRPA combines Windows UI, browser/DOM and image automation with UI inspection, reusable Components and packaging. Executor provides local scheduling and run history, with logs and optional screen recordings for investigating failures.

Mature commercial RPA platforms and established open-source projects cover many of these needs. My focus is bringing them together around Python implementation and a visible process.

About this release

I started LiberRPA because I enjoy automation engineering and wanted to build a tool I'd want to use myself. I shared it here in July 2025; other commitments and further polishing kept me from posting again until now.

The capabilities above span several releases. 0.3.0 adds Component Management, alongside usability improvements, bug fixes, better logging, security hardening and documentation updates.

LiberRPA 0.3.0 is Windows-only, requires Python experience and is still alpha. It is licensed under AGPL-3.0-or-later, with no LiberRPA license fee.

A central Console for multiple Executors is planned as open-source software with no LiberRPA license fee, allowing deployment on your own infrastructure and control over your data.

The aim throughout is to help the next developer follow the process, change the code and investigate the result.

Source code, downloads and documentation

On the last automation you inherited or maintained, what was hardest to work out—and how did your tool help or get in the way?

An example from your existing workflow is enough; you don't need to install LiberRPA.


r/rpa • • May 05 '21

Upcoming RPA Conferences

27 Upvotes

(I'm not affiliated with any of the RPA vendors, just an enthusiast.)

Just letting you know there are a few conferences coming up, all online and free.

In date order:

May 11-13 Automation Anywhere Imagine (https://imagine.automationanywhere.com/)

May 18-20 Blue Prism World (https://events.blueprism.com/blue-prism-world)

June 15-16 UiPath DevCon (https://www.uipath.com/events/devcon)

Enjoy!


r/rpa • • Jun 09 '26

Looking for RPA professionals transitioning to AI Engineering (Agentic AI) – Study Group

26 Upvotes

I'm looking for like-minded people who are planning to transition from RPA into AI Engineering, with a particular focus on Agentic AI.

My goal is to build on my existing RPA experience rather than start from scratch, and pivot into AI engineering in a way that keeps my automation background relevant.

I work full-time in RPA, so staying consistent with learning after work can be challenging. I'm looking for people who can help keep each other accountable and collaborate on projects.

I already have a learning roadmap in mind, and I learn best by building things, so I'd love to work on problem-solving exercises and real-world projects together instead of just watching courses.

Ideally, I'm looking for people who already have some industry experience and understand the challenge of balancing a full-time job with upskilling.

If there's enough interest, we can create a WhatsApp or Discord study group, whatever works best, and learn together while working toward the AI engineering/agentic AI space.

If this sounds like something you'd be interested in, drop a comment or send me a DM.


r/rpa • • Aug 01 '25

DocStrange - Open Source Document Data Extractor

Thumbnail
gallery
26 Upvotes

Sharing DocStrange, an open-source Python library that makes document data extraction easy.

  • Universal Input: PDFs, Images, Word docs, PowerPoint, Excel

  • Multiple Outputs: Clean Markdown, structured JSON, CSV tables, formatted HTML

  • Smart Extraction: Specify exact fields you want (e.g., "invoice_number", "total_amount")

  • Schema Support: Define JSON schemas for consistent structured output

Data Processing Options

  • Cloud Mode: Fast and free processing with minimal setup

  • Local Mode: Complete privacy - all processing happens on your machine, no data sent anywhere, works on both cpu and gpu

Quick start:

from docstrange import DocumentExtractor

extractor = DocumentExtractor()
result = extractor.extract("research_paper.pdf")

# Get clean markdown for LLM training
markdown = result.extract_markdown()

CLI

pip install docstrange
docstrange document.pdf --output json --extract-fields title author date

Links:


r/rpa • • Nov 12 '25

How does Blue Prism have any market share?

25 Upvotes

Gentlemen, I think I have fucked up.

I'm an experienced uipath rpa dev, I'm fluent in python and I've worked with the Power platform as well. Suffice to say I'm a fairly experienced automation developer and that I know my way around a fair few techs.

I recently got a new job at another company which uses BP for their automation agenda or whatever you call it. I had heard of it and played around with it at home before I started and didn't really get it - coming from uipath it feels like opening notepad in terms of ux and basic functionality. But I figured that I probably just didn't know it will enough and that I was just overlooking something, so I figured that I would get a better opinion of it once I started.

Well, fast forward to about two weeks into my new job, and I'm left wondering how tf BP has any market share left in the industry? It's so bare bones and basic both in terms of ux, integrations and IDE functionality that I'm just baffled how anyone still uses it. There's not even any meaningful kind of intellisense or other commonplace niceties for Pete's sake. How does anyone like working with this? I legitimately fear becoming worse at what I do if I have to keep working with this for any amount of time - if for no other reason than banging my head on my desk in frustration at how fucking ancient and backwards this seems.

Has anyone else had this experience or am I being totally unreasonable?


r/rpa • • Jan 19 '25

Is agentic AI really going to replace traditional RPA?

25 Upvotes

I have been seeing this topic showing up so much more frequently these days. My understanding is

  1. Many organisations still uses legacy systems and traditional RPA is still the most cost-effective solutions for them.

  2. Security, To truly have E2E automation, we usually require a combination of tools, execution by AI still needs backend integration while traditional RPA can do most of them without API.

What are your thoughts?


r/rpa • • Dec 16 '22

Power Automate vs UiPath vs Automation Anywhere

25 Upvotes

Hi all

I am new to this area and currently comparing the above, what would be the justification be for going for UiPath or Automation Anywhere over the MS stack ie Power Automate, if you are an MS shop.

Are there any good comparison documents on this or what have seen your own experiences.

If you had your time again what would you go with?

Thanks


r/rpa • • Jun 16 '26

Our best agent still fails 3 in 10 complex enterprise tasks in our benchmarks. quick take on rpa vs agents and how we see it going forward.

24 Upvotes

Hi everyone, Gabriel from UiPath here, with a soft spot for RPA tbh. I wanted to post this for a long time, with one major reason: the "RPA is dead in 2026" vibe is all over the place right now, even in this sub, but i feel its mostly from people who don't build automations for a living, and I'd rather have the conversation with the people who do.  

We recently ran an Agent benchmark that's relevant, so I'm sharing the numbers and what I make of them. Let me hear your own thoughs after. 

So, we built UI-CUBE to test computer-use agents on real enterprise work: multi-step flows in mocked Salesforce, SAP, Workday and Concur, graded by strict pass/fail on the app state, not by an LLM judge. 

Two source notes: 

  • 2025 run is published and auditable: repo / writeup  

  • 2026 numbers below are from customer-facing materials, cleared for external use but not on the research page yet. I've asked for that to be fixed. 

The numbers Agents delivered: 

  • in Oct 2025, published: best was our Screen Agent w/ GPT-5 at 17.4%. Claude Computer Use 4.0 8.7%, OpenAI computer-use-preview 10.4% 

  • in mid-2026: our best config (Screen Agent w/ Gemini 3.5 Flash Preview) 70%, GPT 5.5 config 65%. Simple tier is basically solved, 90%+ 

  • two caveats: the suite grew 226 → 298 tasks between runs, so the jump is directional, not really clean. And yes, ours tops this benchmark with our own CV model in. Home advantage. Real, but not the point if this talk. 

Why agents still break on the hard tier 

  • they're fine on atomic clicks. They fall apart over long sequences where one mistake voids the whole run. 

  • the failure modes are the disqualifying kind: losing track of which items they've processed, repeating or skipping steps, and inventing values for fields meant to stay empty.  

  • the real problem isn't pass rate, it's variance. Same input today and tomorrow gives you a similar output, not the same one. For reconciliation/payroll/compliance, "similar" means no go. 

  • realistically, a 70% agent with that habit is more dangerous than a 17% one, because someone will actually ship it 

  • know limitation: in the Oct run agents were capped at 50 steps while human evaluators averaged 75+ on some tasks, so part of the tier was unwinnable by construction. But the failures above show up early in runs, not at the cap 

RPA's side, since I'm not here to pretend it's flawless 

  • selectors break when the UI changes. Our own eng blog calls them fragile, in writing. 

  • rules have no judgment: the off input, the unmapped exception, the moved field. You've all lost weekends to it 

  • so it's a failure-mode trade: the bot breaks loudly when the UI shifts, the agent quietly hands you a different answer each day 

Cost 

  • an agent re-reasons every run: screenshot → model call → action, every step, every time. Inference bill on each execution 

  • deterministic automation front-loads the cost (build + maintenance), then runs at near-zero per run 

  • neither is free, they just bank the cost differently. Agents: cheap to start, cost scales with usage. Deterministic: pricier to stand up, then flat. At a few thousand runs/month the per-run math isn't close 

Where I land: RPA + agents, not either alone 

  • put the probabilistic part only where determinism is fragile, at the smallest scope that works 

  • example: selector fallback chain → strict, then fuzzy, then semantic, then CV. You only pay the agent cost when the deterministic path breaks. The bottom of that chain (we call it Healing Agent) tries to repair a broken selector at runtime: close a pop-up, swap a selector, add a delay. It's recovery, not immunity, there's a known-limitations page right next to it 

  • same shape at the top: deterministic workflow runs the 150-step sequence, an agent takes the one "outside the rules" step that needs judgment 

Where I might be wrong 

  • the slope is the best counter to my own point: 17% → 70% in eight months (17% → 65% if you hold the engine roughly constant, GPT-5 → GPT 5.5). If that holds, the hard tier gets good fast 

  • what the slope doesn't fix is reproducibility, which is the part that matters most for the work this sub does 

  • and if your processes are low-volume, variance-tolerant and change weekly, an agent alone is probably the better call than maintaining a bot 

 

Do we have it right, or does your day-to-day work say different? We would love to hear from you, lets talk!


r/rpa • • Feb 22 '26

Switching out from RPA : Have already hit a ceiling

24 Upvotes

I want guidance to switch out from rpa. I have already spent 5 years into this and feels liks hitting a ceiling I dont see much career growth. I have learnt MERN basics but the ai buzz is confusing me. Should i upskill myself to full stack or ai roles? Has anyone done a similar switch? Please guide.!!!!


r/rpa • • Nov 21 '25

RPA is supposedly DEAD again and I’m trying to figure out where that leaves people like me

24 Upvotes

lately my feed has been full of folks saying that everything is shifting to LLM-driven agents and that RPA is basically on its last legs. then the next post claims both things will blend into this APA setup where rules-based stuff meets agent-style reasoning. it all feels divided and a little chaotic.

my background leans way more into agent frameworks like LangGraph, Autogen, CrewAI and similar tools. that’s the space I’ve been learning and building in. but every time I dig deeper, I run into people saying companies won’t lean too heavily on pure agent builds because they’re pricey to run and harder to control. and that most teams will mix RPA with agentic layers instead.

right now it just feels super messy. APA does sounds interesting, but it also feels like the label keeps shifting depending on who’s talking about it. meanwhile I’m sitting here trying to figure out whether sticking with agent tooling puts me in a good spot or a weird one.

so I’m hoping to hear from folks who’ve actually dealt with this mix in real setups, not just theory. any direction that helps me understand the landscape would mean a lot. thanks


r/rpa • • Dec 26 '24

RPA YOUTUBE with the intention of sharing technical and in-depth content

24 Upvotes

Hey guys, how are you?

I have the idea of ​​sharing the knowledge I acquired over the years working with RPA, focusing mainly on Python and the best-known libraries such as Selenium, BS4 and Requests. My proposal is to create a playlist that goes from the basics to the creation of a well-structured project, covering everything from a modular architecture, through the creation of a pipeline in Docker, to production on platforms such as Azure or AWS.

The objective is to cover the bases of RPA, the libraries used, automation strategies, requirements gathering, PDD, SDD, flowcharts, among other practices that really add value to the professional.

I am not looking to sell courses, as I believe that knowledge is available in books and documentation. I also want to cover future concepts, such as the use of LLM for pattern recognition in webscraping, low-code, GOF in Python and how this can be useful, among other topics.

My question is: in your opinion, does it make sense to create a channel with this focus? If it doesn't make sense, I'd love to hear your opinions. If you do, I welcome suggestions for the content! It will be a pleasure!


r/rpa • • Apr 10 '21

Any better solution than Automation Anywhere

24 Upvotes

The title sums it up, i came here after 2 weeks struggling with how glitchy object cloning in AA be. It just breaks left and right and incapable of clicking OK button sometimes (which is very big and identifiable). I just need something neat and straightforward that the end-user can wrap their mind around it. Nothing some bloody thing that fails even in basic command and god dont get me started in replacing “CLICKING A GODDAMN BUTTON” with macro, script, and metabot. Thanks