Which tasks really lend themselves to it
A lot of work goes through the browser that calls for no particular skill. Logging into a members' area, filling in the same form over and over, uploading a document, downloading the receipt and noting somewhere that you downloaded it
The practical rule is this. If you can explain to a new colleague what to click without ever saying the words it depends, that piece can be handed to a system
Where you have to read the context instead, choose case by case or pick up the phone, a person stays, and that's how it should be
How a browser automation works
There's nothing magic underneath. The system opens the browser the way you would open it, goes to the right address, waits for the page to be ready, types into the fields, presses the button
Then it reads what the site answers back, and that's the most important piece of all, even though it's the one people think of last. Until you have read the final message you don't know whether the operation went through
A job done properly also keeps a log, the date, the document it touched, the reference number the portal gave back. You need it the day somebody asks what happened on the 12th of last month
The fragile part is the fields on the page
The system has to find the fields again every time, and the way it finds them decides how long it will hold up
If you hook it to the position, say the third field at the top right, the portal only has to move one thing and it breaks. If you hook it to something stable instead, like the field's identifier or the label written beside it, it lasts far longer
Same story with the waiting. The classic mistake is taking for granted that the page has already loaded. A serious system waits until the element is really there, it doesn't count to three and hope that's enough
Logins and credentials, with no shortcuts
Passwords don't get written inside the automation. They stay outside, somewhere you can change without going back over everything else
Where it's possible, a dedicated account for the system is worth having. That way the portal's own log tells you what the automation did apart from what the people did, and if one day you want to unplug everything, disabling that account is enough
If the portal asks for a code on your phone at every login, the whole thing gets harder. Sometimes a session that lasts over time solves it, sometimes it simply doesn't, and it's better to know that before starting than to find out later
Then the site changes, and that has to be expected
Portals change. They add a banner, move a button, rebuild the form, and when that happens the automation has to be fixed. It isn't a flaw in the work that was done, it's the nature of the thing
So it's better to think of it as something to keep standing over time, and not as a job that ends on delivery day
One precaution changes a lot. If the system stops and warns you when it can't find a field, instead of carrying on, a change to the portal costs you one alert and not a hundred botched cases to redo by hand
When it's better to drop it
The first thing to look at isn't whether it can be done technically, it's what the site's terms of use say, because some portals forbid automated activity, others put checks in place on purpose to block it, and forcing those isn't a sensible route
Then there's the most obvious case of all. If the portal already offers a direct integration or a file you can import, use that, it's sturdier than the browser and it doesn't break when they change the color of a button
And if you do an operation three times a month, you will never get back the time you spend keeping it running, so keep it by hand without regrets
How much time you're really leaving there
Before the technical talk you need a number. Take how many times a month you do that operation, multiply by the minutes it takes away each time, and you have the hours
To those add what the quick sum leaves out, the time to redo the botched cases, the interruptions, the peak days when the backlog builds up and somebody stays late
Let's do a made-up sum just to show the method. Say three hundred cases a month at six minutes each, that's thirty hours, a figure big enough to justify the work. If the same sum gives you two hours instead, you have already answered yourself
The numbers in the example mean nothing, do it again with yours
The next step
If the sum works out, the most useful step is to look at the process as it really is, which pages you touch, in what order, what happens when something goes wrong and how many operations you do in a month
From there it takes little time to see whether it makes sense or not, and knowing that it doesn't is still an answer that saves you money