RPA 与 Selenium
A robot that drives software through its screen, exactly as a person would.
RPA stands for Robotic Process Automation, which sounds far grander than it is. A program clicks the buttons and fills the fields that a person would. Selenium is the best-known tool for doing that inside a web browser.
It matters because of a problem every SME hits eventually: the system holding your data has no proper way to talk to other software. Old accounting packages, supplier portals, government sites, that one industry tool nobody has updated since 2014. No API, no export worth having, and the vendor is not going to build one for you.
RPA is the way in. If a person can do it on a screen, this can usually do it too — at 6am, every day, without getting bored on the fortieth record. It is also the most fragile thing on this page, and anyone who tells you otherwise has not maintained one.
Every morning someone logs into three supplier portals, downloads a stock file from each, opens them, copies the columns that matter into a master sheet, and fixes the formatting. Forty minutes, and it is the least interesting part of their job.
At 6am the robot has done all three and left one clean file where the reporting picks it up. Your person opens a finished sheet. On the day a portal changes its layout, they get an email instead of a surprise.
How we actually build it
-
01
We watch someone do it once
Every click, every field, including the bits they do without thinking.
-
02
We script exactly that
Anchored to stable things on the page rather than pixel positions, so a small layout change does not break it.
-
03
We add checks
Did the page load? Did the number look sane? Did the save actually save? A robot that fails loudly is far better than one that fails quietly.
-
04
We schedule and monitor it
It runs on its own and emails you if the site changed under it.
- The system has no API and the vendor will not build one
- Someone logs into a portal every day to copy the same numbers out
- A supplier or bank site has to be checked on a schedule
- A proper API exists — always use it, it is faster and far less fragile
- The screen layout changes often; the robot breaks whenever the page moves
- It needs a login you are not permitted to automate. Check the terms first
- A login the automation is permitted to use
- Confirmation that automating it does not breach the site's terms
- A person to call when a source system changes
1–2 weeks per portal. Budget a little ongoing time for maintenance — this is the one that needs it.
What people ask about this
Is this allowed?
Usually, for your own accounts and your own data — but check the terms of any third-party site first. We will raise it if something looks like it crosses a line rather than build it quietly.
What happens when the website changes?
It breaks, and it tells you. That is why we build the checks. Expect a small maintenance touch once or twice a year per portal.
Often paired with
Would this work for you?
The first call is free, and we will say plainly if this is the wrong tool for your problem.
预约免费通话