Automating portal work when there is no API

Most business portals have no API or import. A practical look at your options, from manual work and scripts to RPA and AI computer workers, and how to pick the first job to automate.

Operon team2 min read

Insurer portals, government sites, supplier dashboards, bank and payment portals: a lot of daily operations work happens in web apps that offer no API and no bulk import. If a person can do it in a browser, though, it can be automated. The question is how.

Your options

Keep doing it by hand

Fine for a few records a month. It stops being fine when one person spends hours a week on it, or when mistakes start costing money.

Write a browser script

Tools like Playwright or Selenium can drive a browser from code. Scripts are fast and precise, but someone has to write them, keep logins safe, and fix them every time the site changes. Without an engineer on hand, they tend to rot.

Use RPA

Robotic process automation tools record and replay clicks. They work well for stable, high-volume processes, but setting them up and maintaining them usually needs specialists and licences sized for larger companies.

Use an AI computer worker

An AI computer worker reads the page and works out the steps from a plain description. No code and no selectors, and it can cope with small page changes. The cost is that AI steps are slower and cost more than fixed scripts.

Operon combines the two: the AI works a job out once, then the steps that worked are saved as a skill and replayed without the AI.

How to pick your first job

Good first jobs share a few traits:

  1. Repetitive. The same steps every time, with different inputs.
  2. Read-heavy or easy to check. Reading a table into a CSV is a gentle start; a final submit is better left for later.
  3. Annoying, not risky. Something the team dreads, where a mistake is cheap to fix.
  4. Clear inputs and outputs. “From this sheet, into that portal” or “from this dashboard, into a CSV”.

Examples: weekly dues reports, quote forms from documents, document uploads.

Things to check before automating

  • Terms of use. Make sure automated use of the portal is allowed for your account.
  • Logins. Use an account meant for the job, and keep the password in a vault, not in a sheet.
  • Final actions. Decide which steps need a human. Operon pauses before submit, pay, finish and delete by default.
  • Captchas and OTPs. These should come back to a person. Operon hands them to you.

A simple rollout

  1. Run the job once while you watch.
  2. Save it as a skill and replay it a few times with different inputs.
  3. Put it on a schedule when you trust it.
  4. Keep the run emails on, so failures reach you.

Start free and try it on one portal job this week.

More from the blog

2 min read

How Operon keeps you in control: safety pauses, the vault and live view

Handing web work to an AI raises fair questions. Here is exactly when Operon stops and asks, how your logins are stored, and how you can watch and take over any run.

Read post
2 min read

Teach once or describe in chat: two ways to hand a job to Operon

You can start an Operon job by describing it in plain words or by showing it once. When to use each, and how both end up as a reusable skill.

Read post
Free trial

Hand off your first job today

Sign up, describe a browser job you do every week, and watch Operon do it. Save it as a skill when it works.