home / use cases / web automation and research / web-form-filing

Recurring portal filings, minus the typing

An Aivell pulls the figures from your database and types them into the official portal — customs declarations, insurance notifications, agency returns — one form at a time, exactly like a clerk. Anything uncertain is saved as a draft for review, and high-value submissions wait for a human yes.

Watch the demo

starts when: Wednesday's filing run — or the request lands by email

The problem

Some portals you visit once a year. Others own a piece of your week: the customs declaration for every cross-border shipment, the insurer’s claim notifications, the agency return that’s due each month. The data already sits complete in your own system — and the portal has no import, so a person retypes it, field by field, shipment by shipment, with a browser tab on each screen.

Retyping between systems that will never be integrated is precisely the work automation should have taken years ago — analysts reckon around 45% of professional-services work is automatable with current technology — but the official portals only speak “human with a browser”. So it stayed manual.

How your Aivell does it

  1. The run starts on your rhythm. Wednesday’s schedule, or an email that says “file these” — the chore picks up the week’s records from your database, read-only.
  2. The Browser Agent does the typing. It opens the portal, starts one declaration per shipment, and fills each field from the record — commodity codes, weights, values, origin — like a very patient clerk.
  3. It checks before it commits. Totals are re-verified against the database before any submission. A field the record can’t answer doesn’t get a guess; it gets a draft and a question to Tomás.
  4. Big ones wait for a person. Over €25,000, the guardrail blocks the submit action itself. The declaration sits complete as a draft; Tomás reviews and presses the button.
  5. Proof is collected on the way out. Each submission receipt is downloaded and filed against its shipment number, and the day ends with a three-line report: submitted, drafted, skipped.

Nothing here needed the authority to be trusted blindly. The chore describes the routine in plain language; the guardrails decide what it may reach and what it may never press. The typing goes; the accountability stays.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · file weekly customs declarations ● active

every wednesday, pull the week's cross-border shipments from the database

open the customs portal and start one declaration per shipment

fill the form from the record — codes, weights, values, origin

re-check the totals against the database before moving on

any field the record can't fill — save as draft, ask Tomás

shipment value over €25,000? draft only, Tomás submits himself

download each submission receipt, file it with the shipment number

email Tomás the day's list — submitted, drafted, skipped

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Browser Agent opens the portal, fills the form
Database supplies the records, read-only
Email reports submitted, drafted, skipped

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Browser Agent Only the customs portal's domain is reachable. On declarations over €25,000, the submit action itself is blocked — draft is as far as it goes.
Database Read-only. Filing can quote your records, never alter them.

Questions, answered.

Will it ever submit something wrong? +

The chore is built so it would rather not submit at all. Every form is checked against the database before submission, any field the record can't fill becomes a draft with a question, and above your threshold the guardrail removes the submit button entirely — a human presses it.

What if the portal times out halfway through a form? +

The Aivell notices — it's watching the actual page, not firing requests blind. It saves a draft where the portal allows one, reports exactly what state each declaration reached, and never files the same shipment twice.

Does our shipment data pass through some cloud robot? +

No. The browser runs on the box, in your office. Data travels from your database straight to the government's portal over your own connection — the same path as a clerk typing, with no automation vendor in between.

We file on three different portals. Three systems to buy? +

One box, three chores — or one chore with three sections, if the rhythm is shared. Each portal gets its own whitelist and its own rules, written in plain language.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee