Browser agents for the systems with no API.
Supplier portals, older ERPs, the admin tool IT built in 2011. A Trelium browser agent logs in and does the work on screen, as one step in the same workflow as your integrations.
Example: checking a supplier portal that has no API
Most steps run on integrations. The browser covers the rest.
A typical run touches several systems. Trelium connects to each one the most direct way it can: a connector if one exists, the API if not, and the browser for the portal that offers neither. You don't have to wait for a vendor to ship an API first.
Browse integrationsExample run
Supplier Status Agent- Read the customer's status requestGmailIntegration
Find the open PO and supplierNetSuiteAPI- Check shipment status on the portalSupplier portalNo APIBrowser
- Write ship date and trackingNetSuiteIntegration
- Reply with trackingGmailIntegration
- 01
Native integration
Over 3,200 prebuilt connectors. Used whenever one supports the task.
- 02
Direct API
No connector, but the system has an API? The agent calls it directly.
- 03
Browser agent
No API either? The agent uses the web app the way your team does.
You describe the task. The agent works out the clicks.
You build a browser agent the same way as any other Trelium agent, and you can read every step it plans to take before it runs.
- 01
Describe the task
Say which web app to use and what finished looks like, e.g. look up each open PO on the supplier portal and copy the ship date.
- 02
Review the steps
The agent turns the screens and fields it needs into a workflow you can read and edit before it runs.
- 03
Run it
Repeat runs follow the same steps, so they stay fast and cheap. The model only gets involved when a screen needs a judgment call.
- 04
Handle exceptions
If a page has changed or a value is missing, the agent tries to fix it and retry. If it can't, it stops and asks someone.
Where teams use browser agents.
Usually it's a site someone logs into every day just to copy information into another system.
Supplier portals
Look up order status and tracking, and download invoices from vendors that don't send a feed.
Legacy ERP screens
Key in orders and update records in older systems that only have a web interface.
Customer portals
Submit quotes, upload proofs, and confirm POs in the portals your customers make you use.
Carrier and freight sites
Track shipments and book pickups on carrier sites that don't connect to your other systems.
Government and tax sites
Prepare recurring filings and certificate lookups, with a person signing off before anything is submitted.
Internal admin tools
Work in the internal tools your team built years ago and never gave an API.
Browser steps follow the same rules as the rest.
You don't need separate controls for browser automation. A browser step lives in the same workflow, needs the same approvals, and is logged in the same run history.
Review step
Waiting on youAgent paused before submitting on the supplier portal
Return request for PO-1842
- Reason
- Wrong size run
- Units
- 48 of 240
Only the apps you pick
A browser agent works in the web apps you set for that workflow. It doesn't browse the open web.
Approval before submit
Put a review step in front of anything that saves, sends, or files. The agent waits until someone approves.
A record of every run
Each run shows the tasks the agent completed and the credits it used.
Available on-prem
If you self-host Trelium, browser agents can reach internal web apps that aren't on the internet.
FAQ
Common questions about browser agents
It's a step in a Trelium agent that uses a web app through its interface. It opens pages, fills in fields, clicks buttons, and reads what comes back. Trelium uses one when a system has no connector or API for the task.
Only when nothing else works. Trelium uses a native integration if there is one, then the system's API, and the browser as a last resort. Plenty of workflows use all three. The example on this page reads a supplier portal in the browser and writes the result to NetSuite.
Routine runs follow a saved set of steps, so minor layout changes usually don't matter. If a page has changed enough to confuse the agent, it tries to work out what moved and retry. If it still can't finish, it stops and flags the run for someone to look at.
Yes. Add an approval step before anything sensitive, like submitting a form. The agent fills everything in, then waits for someone on your team to approve it.
Yes, if you run Trelium on-premises. It sits inside your network, so browser agents can use internal tools and older systems that aren't exposed to the internet.
Have a portal with no API?Bring it to the demo.
Show us the site and the task. We'll walk through how a Trelium agent would handle it next to the systems you already connect.