To automate a supplier portal or any website without an integration, you need something that signs in and works the site in a browser, as a person would: a scripted macro, or an AI agent that reads each page. Kaer is the second kind. It uses a direct connection where it has one and its own sandboxed browser everywhere else.
If you can log in, Kaer can work it.
That holds for sites that work in an ordinary browser. When a site blocks automated browsers outright, Kaer tells you and offers you control instead of trying to get past it.
This post is about choosing an approach and knowing where it should stop. For the steps in the app, follow the guide to getting work done on a website with no integration. For the wider question of when an agent fits better than a fixed chain of triggers, read AI agents versus workflow automation first.
Why do so many business tools have no integration?
Because integrations get built where enough customers ask for them, and much of the software a small business depends on has too few users to justify one. A wholesaler's trade portal, a venue's booking system, the back-office tool an industry has used for years: each serves its own customers well and connects to nothing else.
Call it login-only software: you reach it through a sign-in page and the only way to get anything out of it is to click. Most workflow automation runs on integrations, so this work stays with a person who signs in every month, finds the invoice, downloads it and files it. The job is small enough that nobody fixes it and frequent enough that it never goes away.
The integrations directory shows which tools Kaer connects to directly and which it works in its own browser. Most of the tools listed there are in the second group, QuickBooks and Xero among them.
How does an AI agent work a website without an integration?
It opens the site in a real web browser, reads the page, then clicks, types and downloads until the job is done, as a person at a keyboard would. A browser automation AI agent differs from a recorded macro in one respect that matters: it reads the page each time instead of replaying fixed positions, so a moved button or a new banner does not have to stop it.
Kaer does this on its own sandboxed computer, a separate machine with a real browser and terminal, kept apart from yours. If something goes wrong on a website, it goes wrong on Kaer's machine, not on your laptop, and idle machines are shut down.
You describe the job in a Work chat and watch it happen in a live browser beside the chat, labelled Errand.
Connector, RPA or AI agent in a browser: which should you use?
Use a connector when the tool has one. Use a scripted macro or RPA when the same steps run in large volumes on a page that rarely changes. Use an AI agent in a browser when nothing connects to the tool and the job needs someone to read what is on the page.
| Connector | Scripted RPA or browser macro | AI agent in a browser | |
|---|---|---|---|
| How it works | Exchanges data with the tool through an integration built for software | Replays a recorded or scripted sequence of clicks and keystrokes | Reads the page in front of it and decides the next step, as a person would |
| Setup | Connect once and grant access | Someone records or writes each step, then tests it | Describe the job in plain words |
| What breaks it | The tool changes or retires the integration, or access is revoked | A redesigned page, a moved button, an unexpected pop-up | A site that blocks automated browsers, or a page it misreads |
| Who handles logins | You authorise through the tool's own sign-in; access is scoped and revocable | Usually a stored credential the script signs in with | Depends on the product. In Kaer, you type passwords and codes yourself |
| Approvals | Whatever the platform enforces. In Kaer, sending email and posting to Slack wait for you by default | Only where someone designs them into the process | In Kaer, a click that pays, books or confirms waits for Approve |
| Best for | Any tool that has one | High-volume runs that never vary | Tools nothing connects to, and jobs that need reading |
Connectors are the first choice wherever they exist: fast, scoped and indifferent to page layout, which is why Kaer uses one wherever it has one. Kaer also has its own public API, so your own systems can send work the other way; handing jobs to Kaer through its API covers that side.
Is an AI agent an RPA alternative?
For some jobs. Scripted automation is quick and predictable while the page stays the same, which suits large volumes of identical runs, but someone has to build each step and repair the script when the site changes. An agent takes a plain-language brief and reads the page as it goes, which suits smaller volumes on sites that change. It is slower per run than a script and can misread a page, which is why the clicks that commit you to something should wait for a person.
What should an agent never do on its own in a portal?
It should never know your password, get past a security check, or commit you to a payment or booking without your say-so. In Kaer those stops are fixed:
- Passwords, one-time codes and card details. You type them after clicking Take over. Kaer can't see or keep your password.
- Payments, bookings and confirmations. Before a click that pays, books or confirms, Kaer asks: Approve, or Check it myself. Nothing is bought or confirmed until you say so.
- Captchas and sites that block automated browsers. Handed to you, never worked around.
- Access you did not give. It uses only the logins and connections you have given it, and you can revoke any connection at any time from the connectors screen without touching the others.
The rest of what you asked for, such as filling in and sending a form or downloading a statement, it finishes. Each task keeps a list of the steps it took and what you approved.
The full list of gated actions, including email, is in what Kaer will not do without you. Isolation, revocation and data handling are on the security page.
What back-office tasks can you automate this way?
Jobs that sit behind a login, repeat, and end in something you can check, such as a downloaded file or a drafted reminder.
- Downloading invoices from a supplier portal. “Log in to the supplier portal and download this month's invoices” is the whole brief. You sign in; Kaer finds the invoices and files them, in a Google Drive folder for example.
- Checking and holding a booking slot. “Check whether Friday at 14:00 is free and hold it.” Kaer checks the booking system and stops before the click that books, so you approve the hold itself.
- Chasing overdue invoices. Kaer opens QuickBooks or Xero in its own browser, you sign in, and it finds what is overdue and drafts each reminder. Every reminder waits for Approve send. The guide to chasing overdue invoices has the steps.
- Matching payments to bills. Reading transactions and bills side by side to find the payment with no bill behind it.
Once a run works, you can turn it into a workflow so it happens every week with the approval step kept in.
Poor fits exist too. A one-off you could finish faster yourself is not worth briefing, and systems behind a VPN or with an unusual sign-in need a conversation with Kaer first.
How do you start?
Pick the portal you dread logging in to and hand over one job. The agent's own computer and browser come with paid plans, and the pricing page shows what each plan includes. The step-by-step guide for websites with no integration walks through every screen.
Frequently asked questions
Can an AI agent automate a website that has no integration?
Yes, if the site works in an ordinary browser. Kaer signs in and works the site in its own sandboxed browser, the way a person would. Some sites block automated browsers outright; when one does, Kaer tells you and offers you control rather than trying to get past it.
Do I have to give Kaer my password for a supplier portal?
No. When a site asks for a password, a one-time code or card details, Kaer stops and hands you the browser. You click Take over, type the details yourself, then Hand back. Kaer can't see or keep your password.
Is an AI agent in a browser an alternative to RPA?
For some jobs. Scripted RPA suits large volumes of identical runs on pages that rarely change. An AI agent in a browser suits work that needs someone to read the page, on sites that change, and Kaer stops for approval before it pays, books or confirms anything.
Will Kaer pay for or book anything in a portal without asking?
No. Before a click that pays, books or confirms, Kaer asks you to Approve or Check it myself, and nothing is bought or confirmed until you say so. A payment waits for your approval whether Kaer works through a direct connection or its own browser.
Is a browser session less secure than a direct connection?
It is scoped differently. A direct connection carries explicit, revocable scopes. A browser session runs on Kaer's own isolated machine, uses only the logins you have given it, and shuts down when idle. A payment waits for your approval on either.
Which Kaer plans include the agent's browser?
The agent's own computer and browser come with paid plans. The pricing page shows what each plan includes.
