Start a project

How to automate repetitive website tasks

4 min read

Copying data between websites, filling the same forms, downloading the same reports every morning. Here is which website tasks can be automated, how it works, and when it is worth it.

A desk with two monitors where repetitive website work is done

Most offices have a task like this. Someone opens a website every morning, signs in, clicks through four screens, downloads a report, and copies numbers from it into another system. It takes forty minutes. It has taken forty minutes every working day for three years.

Nobody decided this was a good use of a person. It happened because the two systems do not talk to each other, and a person was the easiest way to connect them.

That kind of work can usually be handed to a script that uses the website the same way a person does. This post explains what can be automated, what cannot, and how to tell whether it is worth doing.

What website task automation is

A browser automation script opens a real browser, goes to a page, types into fields, presses buttons and reads what appears on screen. It does what a person would do, in the same order, without getting bored or skipping a step.

The tool we use for this is Playwright, the same one used for testing. A test checks that a website behaves correctly. An automation uses the same skills to get work done on it.

Tasks that automate well

A task is a good candidate when it has clear steps and the same steps every time.

  • Moving data between systems. Reading orders from one website and entering them into another that has no import feature.
  • Downloading reports. Signing in to a supplier or bank portal each morning and saving the latest file to a shared folder.
  • Filling forms in bulk. Entering two hundred product listings, bookings or registrations from a spreadsheet.
  • Checking for changes. Looking at prices, stock levels or tender listings on a schedule and sending an alert when something changes.
  • Collecting information. Gathering figures from several dashboards into one daily summary.
  • Repeating admin steps. Creating accounts, assigning permissions, or updating records one by one in a system with no bulk option.

Tasks that do not

Being honest about this saves money.

  • Work that needs judgement. Deciding whether a customer complaint deserves a refund is not a sequence of clicks.
  • Sites that forbid it. Some websites prohibit automated access in their terms, and some actively block it. We do not work around those protections.
  • Tasks done once a year. If it takes an hour annually, automating it costs more than it saves.
  • Anything with a proper integration available. If both systems offer an API or a built-in connection, use that. It is more reliable than driving a browser.

How to tell if it is worth it

Work out what the task costs now. Take the minutes it takes, multiply by how often it is done in a year, and you have the hours. Forty minutes every working day is about 170 hours a year.

Then weigh three things against that number.

  1. How stable is the website? A portal that is redesigned every few months will break the script each time, and someone has to repair it.
  2. What does a mistake cost? A person who copies a figure wrongly once a month may be costing more than their time.
  3. Does it block someone? A task that must be done before the team can start work costs more than its own minutes.

As a rough guide, anything that takes more than an hour a week and follows fixed steps is worth looking at.

What a finished automation looks like

A script that works on the developer's laptop is not finished. A dependable one has:

  • A schedule, so it runs without anyone starting it.
  • A clear record of what it did each time: which records, which files, how long.
  • Alerts when something fails, sent to a person, with a screenshot of the page at that moment.
  • Safe handling of passwords, kept out of the script itself.
  • A sensible stop. If the page looks different from what it expects, it should stop and say so. A script that guesses can do damage quickly.

Where AI helps

Websites change, and a traditional script breaks when a button is renamed or moved. Newer automation can use AI to find the right element by what it means, so a "Submit" button renamed to "Send" does not stop the run. This makes automations cheaper to keep alive, though it does not remove the need to check their results. We cover this under AI test automation.

Getting started

Pick one task. Write down every step as you do it, including the ones you no longer notice, and time it. That list is most of what a developer needs to estimate the work.

We build these as a service: see website task automation. If you have a task in mind, tell us what it is and how often you do it, and we will say plainly whether it is worth automating.

Chat with us